Without me changing anything, my Discourse forum https://lilypond.community suddenly started returning an error page for any request with login cookies: Oops The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience. Detailed information ab…

Same error than this: [imagen] Fatal: could not read Username for 'https://github.com' Self-hosting I tried upgrade my 2-container forum, but it fails. Any ideas why? x86_64 arch detected. …

Oh, actually, if I log in with an unprivileged user account, it works, but not with my admin account. So I suspect it’s the upgrade part of the admin interface that’s hanging in these Git operations?

Seen here too. Admins and mods are blocked while things time out, I think. Process tree: 1000 2169778 0.0 0.3 497160 13392 ? Sl Aug17 0:15 | \_ pitchfork monitor - 1000 2169783 0.0 5.4 6554324 212356 ? Sl Aug17 4:55 | | \_ pitchfork …

So DiscourseUpdates.has_unseen_features seems to be a feature which is bringing in a realtime dependency on github working correctly? Even when we’re not trying to upgrade?

I’ve unchecked this feature: admin->site admin → version checks → clear the checkbox → save [image] Site admin Configure various settings relating to the management of your site version_checks Ping the Discourse Hub for version updates and show new version messages on the admin dashboard

How did you manage get the admin interface to open without error in the first place?

I had to wait until the git nonsense timed out, and/or could get my request served to a pitchfork which wasn’t blocked. My forum/logs area is presently showing 4 cases of “pitchfork worker timed out” and it’s not a very busy forum at all.

One could also use rails from an ssh access, I believe. This might be a terrible idea. Proceed at your own risk. # docker exec -i app rails runner 'puts SiteSetting.version_checks' true # docker exec -i app rails runner 'SiteSetting.set("version_checks", false)' # docker exec -i app rails runner …

It seems that Github continue with issues, that were the previous ones: [imagen] The August 17 outage, and the work ahead An update on the August 17 outage and the steps we're taking to improve reliability. Est. reading time: 4 minutes

Error para usuarios conectados y bloqueo de Git

Soporte

Jagster (Jakke Flemming) 2 Septiembre, 2026 19:16 2

El mismo error que este:

Tema		Respuestas	Vistas
40 Fatals and 7 Errors in recent logs Support	12	1741	17 Febrero 2017
Fatal: could not read Username for 'https://github.com' Self-hosting	7	127	3 Septiembre 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7685	22 Octubre 2016
The discourse stopped working with error 500 Internal Server Error Bug	1	3096	7 Marzo 2017
New users can't sign up, 404 errors in console Support discourse-id	25	417	18 Marzo 2026

Error para usuarios conectados y bloqueo de Git

Temas relacionados