Fehler in den Protokollen bezüglich twitter_login

RBoy · 10. Oktober 2025 um 05:34

Nach dem Update auf den heutigen Build 3.6.0 beta 2 sehe ich Fehler in den Protokollen. Ich habe überprüft, ob die Twitter (X) Registrierung und Anmeldung problemlos funktioniert. Ich habe keine Ahnung, warum diese Meldungen ausgegeben werden:

Nachricht (67 Kopien gemeldet)

Ein geplantes Problemprüfung des Admin-Dashboards (twitter_login) ist fehlgeschlagen. : NoMethodError : undefinierte Methode `basic_auth' für eine Instanz von 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 · 15. Oktober 2025 um 07:27

Danke für den Bericht, @RBoy!

Es gab eine Breaking Change in der Faraday-Gem, die als Teil dieser Veröffentlichung aktualisiert wurde. Sie wurde von unseren automatisierten Tests nicht erkannt.

Ein Fix für das Problem wurde gerade hier zusammengeführt:

github.com/discourse/discourse

FIX: Twitter health check broken on Faraday update

main ← fix/twitter-auth-health-check

opened 07:11AM - 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 · 16. Oktober 2025 um 22:04

Während die Fehler in den Protokollen nach dem Update auf die neuesten Commits nicht mehr angezeigt werden, sehe ich diesen Fehler auf dem Dashboard, aber die Twitter-Anmeldung (es ist wahrscheinlich an der Zeit, dass Discourse sie jetzt in X umbenennt) funktioniert weiterhin einwandfrei.

Ist dies ein kosmetisches Problem oder passiert etwas anderes im Hintergrund?

Twitter-Anmeldung scheint im Moment nicht zu funktionieren. Überprüfen Sie die Anmeldeinformationen in den Site-Einstellungen.

Schließen

AktualisierenZuletzt geprüft: 16. Oktober 2025 18:00 Uhr

tgxworld · 24. Oktober 2025 um 08:52

Der Fehler wurde behoben in

github.com/discourse/discourse

FIX: Twitter login problem check not reporting accurately

main ← fix_twitter_login_problem_check

opened 08:49AM - 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 · 27. Oktober 2025 um 00:00

Dieses Thema wurde nach 11 Tagen automatisch geschlossen. Neue Antworten sind nicht mehr möglich.

Thema		Antworten	Aufrufe
Twitter denying API calls SSO	3	171	24. Juni 2024
Twitter Login and signup error Support	5	4618	8. Juni 2024
Twitter & Google login not working any more Support	7	1351	29. März 2022
Twitter login doesn't work on meta Site feedback	5	1394	22. Juni 2024
Configuring Twitter login and rich embeds for Discourse Integrations sso , how-to , social-auth	142	226410	28. August 2025

Fehler in den Protokollen bezüglich twitter_login

Verwandte Themen