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

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

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

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

지원

jeanas (Jean Abou Samra) 9월 3, 2026, 12:01오후 14

제 포럼도 다시 정상 작동하고 있습니다. 하지만 문제는 여전히 근본적으로 해결되지 않았습니다: GitHub의 장애가 Discourse 포럼의 장애로 이어져서는 안 되니까요.

글		댓글	조회수
Fatal: could not read Username for 'https://github.com' Self-hosting	10	345	9월 3, 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7815	10월 22, 2016
40 Fatals and 7 Errors in recent logs Support	12	1814	2월 17, 2017
Locked out of my forum after restore Support	19	668	1월 27, 2025
Discourse now stops loading at login dialog when viewed with any browser Self-hosting	21	1518	1월 29, 2023

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

Related topics