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…

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…

Confirmed, they are still having issues in their systems: fatal: remote error: GitHub is temporarily limiting some unauthenticated downloads to protect the stability of the platform. Please retry later or authenticate. could not read Username for '``https://github.com/``': No such device or addres…

[이미지] satonotdead: they are still having issues in their systems On the github issue it seems people (at least in Europe) are seeing the problem is resolved. It seems OK for me (my servers are in Finland) Anyone confirm they still have a problem?

My own forum is working again as well. However, the issue is certainly not solved in general: an outage of GitHub shouldn’t cause an outage of Discourse forums in the first place.

Yet it does, because any reason why rebuilding of a container fails, will kill Discourse (and that’s why we have an option: 2-container setup). But sure. It would be nice if the app-container would survive.

[이미지] jeanas: an outage of GitHub shouldn’t cause an outage of Discourse forums in the first place. I completely agree. And in my case, there was no rebuild or other intentional git action. These were I think ‘helpful’ git actions which turned out not to be helpful. I would like my self-host…

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

지원

Falco (Falco) 9월 3, 2026, 5:14오후 25

좋아요, PR을 병합했습니다. 운영 중인 릴리스 채널에 반영되면 알려주시고, 그 후 며칠간 기다려서 GitHub이 다시 중단되는 동안 어떻게 되는지 알려주세요.

글		댓글	조회수
Fatal: could not read Username for 'https://github.com' Self-hosting	10	247	9월 3, 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7713	10월 22, 2016
40 Fatals and 7 Errors in recent logs Support	12	1745	2월 17, 2017
Admin users always get 500 timeout in GitUtils.has_commit?, while normal users work fine Bug	0	79	7월 6, 2026
Google Login Stopped Working after manual update Support	5	1053	3월 8, 2019

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

Related topics