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…

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

[imagem] 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 so…

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…

[imagem] 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.

[imagem] 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-h…

[imagem] 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.

[imagem] Ed_S: I would like my self-hosted forum to run unattended even if And it will — unless an admin says .launcher rebuild app. Or what am I missing now?

Erro para usuários conectados e travamento do Git

Suporte

jeanas (Jean Abou Samra) Setembro 3, 2026, 12:01pm 14

Meu próprio fórum também voltou a funcionar. No entanto, o problema certamente não foi resolvido de forma geral: uma interrupção no GitHub não deveria, em primeiro lugar, causar uma interrupção nos fóruns do Discourse.

Tópico		Respostas	Visualizações
The Git Hang and the Admin/Mod user Accs Oops Error Page Error Self-hosting login , bug	28	497	5 de Outubro de 2026
Fatal: could not read Username for 'https://github.com' Self-hosting	10	377	3 de Setembro de 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7842	22 de Outubro de 2016
40 Fatals and 7 Errors in recent logs Support	12	1854	17 de Fevereiro de 2017
Discourse now stops loading at login dialog when viewed with any browser Self-hosting	21	1551	29 de Janeiro de 2023

Erro para usuários conectados e travamento do Git

Tópicos relacionados