# Error en los registros relacionado con twitter\_login **URL:** https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203 **Category:** Bug **Created:** [10 Octubre, 2025 05:34 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203 "2025-10-10T05:34:10Z") **Posts on this page:** 5 **Page:** 1
### Author: ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy) #### Post date: [10 Octubre, 2025 05:34 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/1 "2025-10-10T05:34:10Z")
Después de actualizar a la compilación de hoy 3.6.0 beta 2, estoy viendo errores en los registros. Comprobé que el registro e inicio de sesión de Twitter (X) funciona correctamente. No tengo idea de por qué está arrojando estos mensajes: ```plaintext Mensaje (se informaron 67 copias) Un problema programado del panel de administración (twitter_login) falló. : NoMethodError : método no definido `basic_auth' para una instancia de Faraday::Connection Rastreo /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 ' /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' ``` ---
### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted) #### Post date: [15 Octubre, 2025 07:27 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/5 "2025-10-15T07:27:48Z")
¡Gracias por el informe, @RBoy! 🙏 Hubo un cambio drástico en la gema Faraday que se actualizó como parte de esta versión. No fue detectado por nuestras pruebas automatizadas. Una solución para el problema se acaba de fusionar aquí: > > > \### 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. ---
### Author: ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy) #### Post date: [16 Octubre, 2025 22:04 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/6 "2025-10-16T22:04:00Z")
Aunque los errores en los registros han dejado de aparecer después de actualizar a los últimos commits, estoy viendo este error en el panel, pero el inicio de sesión de Twitter (probablemente sea hora de que Discourse lo cambie a X ahora) sigue funcionando bien. ¿Es un problema estético o está sucediendo algo más en segundo plano? > El inicio de sesión de Twitter parece no funcionar en este momento. Verifique las credenciales en la configuración del sitio. > > Descartar > > Actualizar Última comprobación: 16 de octubre de 2025 18:00 ---
### Author: ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld) #### Post date: [24 Octubre, 2025 08:52 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/8 "2025-10-24T08:52:39Z")
El error se ha corregido en > > > 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. ---
### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted) #### Post date: [27 Octubre, 2025 00:00 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/11 "2025-10-27T00:00:09Z")
Este tema se cerró automáticamente después de 11 días. Ya no se permiten nuevas respuestas.