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: [이미지] 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?

Edit: this did not solve my problem, as I discover after several hours. 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…

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.

Edit: this did not solve my problem, as I discover after several hours. 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 'Sit…

It seems that Github continue with issues, that were the previous ones: [이미지] 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

[이미지] Ed_S: My forum/logs area is presently showing 4 cases of “pitchfork worker timed out” and it’s not a very busy forum at all. I’m now seeing 15 cases of pitchfork worker timed out, with two different backtraces. On the linux side pitchfork continues to accrue unreaped children and somet…

로그인 사용자의 오류 및 Git 정지

제품 지원

Jagster (Jakke Flemming) 9월 2, 2026, 7:16오후 2

이것과 동일한 오류입니다:

글		댓글	조회수
The Git Hang and the Admin/Mod user Accs Oops Error Page Error Self-hosting login , bug	28	608	10월 5, 2026
Fatal: could not read Username for 'https://github.com' Self-hosting	10	418	9월 3, 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7870	10월 22, 2016
40 Fatals and 7 Errors in recent logs Product Support	12	1892	2월 17, 2017
Discourse now stops loading at login dialog when viewed with any browser Self-hosting	21	1560	1월 29, 2023

로그인 사용자의 오류 및 Git 정지

Related topics