twitter_login과 관련 로그 오류

RBoy · 10월 10, 2025, 5:34오전

오늘의 빌드 3.6.0 beta 2로 업데이트한 후 로그에서 오류가 발생하고 있습니다. 확인해 보니 트위터(X) 가입과 로그인은 정상적으로 작동합니다. 왜 이런 메시지가 표시되는지 모르겠습니다:

Message (67 copies reported)

A scheduled admin dashboard problem check (twitter_login) errored. : NoMethodError : undefined method `basic_auth' for an instance of Faraday::Connection

Backtrace

/var/www/discourse/lib/auth/twitter_authenticator.rb:23:in `block in healthy?'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/faraday-2.14.0/lib/faraday/connection.rb:91:in `initialize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/faraday-2.14.0/lib/faraday.rb:99:in `new'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/faraday-2.14.0/lib/faraday.rb:99:in `new'
/var/www/discourse/lib/auth/twitter_authenticator.rb:22:in `healthy?'
/var/www/discourse/app/services/problem_check/twitter_login.rb:9:in `call'
/var/www/discourse/app/models/problem_check.rb:169:in `run'
/var/www/discourse/app/models/problem_check.rb:155:in `run'
/var/www/discourse/app/jobs/regular/run_problem_check.rb:18:in `execute'
/var/www/discourse/app/jobs/base.rb:318:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management.rb:17:in `with_connection'
/var/www/discourse/app/jobs/base.rb:305:in `block in perform'
/var/www/discourse/app/jobs/base.rb:301:in `each'
/var/www/discourse/app/jobs/base.rb:301:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:220:in `execute_job'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:185:in `block (4 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:180:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/lib/sidekiq/discourse_event.rb:6:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/lib/sidekiq/pausable.rb:131:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job/interrupt_handler.rb:9:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:26:in `track'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:134:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:173:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:184:in `block (3 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:145:in `block (6 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_retry.rb:118:in `local'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:144:in `block (5 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/config.rb:39:in `block in <class:Config>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:139:in `block (4 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:281:in `stats'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:134:in `block (3 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_logger.rb:15:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:133:in `block (2 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_retry.rb:85:in `global'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:132:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_logger.rb:40:in `prepare'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:131:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:183:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in `block in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in `process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:86:in `process_one'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:76:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/component.rb:10:in `watchdog'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/component.rb:19:in `block in safe_thread'

ted · 10월 15, 2025, 7:27오전

@RBoy님, 보고해 주셔서 감사합니다!

이번 릴리스에서 업데이트된 Faraday gem에 깨짐 변경(breaking change)이 포함되어 있었습니다. 자동 테스트에서 이를 포착하지 못했습니다.

해당 문제의 수정이 방금 다음 위치에 병합되었습니다:

github.com/discourse/discourse

FIX: Twitter health check broken on Faraday update (#35407)

main ← fix/twitter-auth-health-check

merged 07:27AM - 15 Oct 25 UTC

Drenmi

+11 -9

### What is the problem? Faraday [updated their authentication/authorization …middleware in version 2](https://github.com/lostisland/faraday/pull/1306), which was a breaking change for the Twitter auth health check. ### Why didn't we catch it? The test was manually mocking and stubbing the individual Faraday objects, so the relevant code path wasn't exercised by our tests. ### How does this fix it? - Update the test to use `stub_request` instead. (This correctly catches the deprecated method error.) - Update the health check to use the new middleware.

RBoy · 10월 16, 2025, 10:04오후

최신 커밋으로 업데이트한 후 로그에 표시되던 에러는 더 이상 나타나지 않지만, 대시보드에서는 이 오류가 표시됩니다. 트위터 로그인(아마도 이제 Discourse가 X로 변경해야 할 때인 것 같습니다)은 여전히 정상적으로 작동하고 있습니다.

이것은 단순한 표시 문제일까요, 아니면 백그라운드에서 다른 문제가 발생하고 있는 걸까요?

현재 트위터 로그인이 작동하지 않는 것으로 보입니다. 사이트 설정에서 자격 증명을 확인해 주세요.

무시

새로고침마지막 확인: 2025년 10월 16일 오후 6:00

tgxworld · 10월 24, 2025, 8:52오전

오류가 수정되었습니다.

github.com/discourse/discourse

FIX: Twitter login problem check not reporting accurately (#35593)

main ← fix_twitter_login_problem_check

merged 01:42PM - 24 Oct 25 UTC

tgxworld

+41 -24

This commit fixes a bug where we were using the twitter's oauth2 endpoint to ch…eck if the `twitter_consumer_key` and `twitter_consumer_secret` has been configured correctly. However, the request returns a 403 response code because of a missing required param causing the problem check to fail. Instead of fixing the request, the better thing to do is to ensure we do the same checks that the `omniauth-oauth` gem does so that we are actually validating the oauth flow.

ted · 10월 27, 2025, 12:00오전

이 주제는 11일 후 자동으로 닫혔습니다. 더 이상 새로운 답변을 작성할 수 없습니다.

글		댓글	조회수
Twitter denying API calls SSO	3	327	6월 24, 2024
Twitter Login and signup error Product Support	4	4841	5월 10, 2018
Twitter & Google login not working any more Product Support	7	1965	3월 29, 2022
Twitter login doesn't work on meta Site feedback	4	1628	10월 29, 2023
Configuring X login and rich embeds for Discourse Integrations sso , how-to , social-auth	142	230503	1월 20, 2026

twitter_login과 관련 로그 오류

Related topics