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…

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: [afbeelding] 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

[afbeelding] 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 an…

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…

[afbeelding] 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?

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.

[afbeelding] 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 se…

[afbeelding] Ed_S: I would like my self-hosted forum to run unattended even if github (and discourse.org ) fell into a very deep hole. :100: It is completely unacceptable to be any other way.

Error for logged in users and Git hang

Ondersteuning

jeanas (Jean Abou Samra) 3 september 2026 om 12:01 14

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.

Topic		Antwoorden	Weergaven
Fatal: could not read Username for 'https://github.com' Self-hosting	10	324	3 september 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7803	22 oktober 2016
40 Fatals and 7 Errors in recent logs Support	12	1792	17 februari 2017
Admin users always get 500 timeout in GitUtils.has_commit?, while normal users work fine Bug	0	82	6 juli 2026
Google Login Stopped Working after manual update Support	5	1064	8 maart 2019

Error for logged in users and Git hang

Gerelateerde topics