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…

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.

[image] 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-ho…

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

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

@Ed_S I think I found the issue and I have a PR for it, can you check to see if it touches the area you saw with issues? FIX: Stop new-feature checks reaching GitHub during requests (#43143) main ← new-features-no-git-in-requests …

[image] Falco: FIX: Stop new-feature checks reaching GitHub during requests - Pull Request #43143 - discourse/discourse - GitHub oh, nice, that does seem to me to have the right shape! (Edit: I read the commentary, not the code!) For interest, when you say per process, is that per pitchfork…

On my forum for example, I became suddenly unable to log in without any admin action on my part. The problem isn’t that you can’t upgrade Discourse when GitHub is unreachable, it’s that GitHub being unreachable takes down your forum because Discourse tries to check for upgrades that you could perfor…

[image] Ed_S: For interest, when you say per process, is that per pitchfork? Yes, exactly. I think this was caused by a way way too eager want of telling people about new features, in the current user serializer of all places, paired with a 3 years old change that moved us away from the norm…

[image] Falco: @Ed_S and @jeanas you both admins on the affected instances right? This should only affect admins while GitHub is down. Yes, exactly, I could log in with another account but not with my admin account.

Cool I have merged the PR . Update when it hits the release channel you run, then wait a couple of days for GitHub to go down again and let me know how it goes during it.

Erreur pour les utilisateurs connectés et blocage de Git

Soutien

agemo (agemo) Septembre 24, 2026, 9:11 34

Ok, cette instance est un droplet DO basé aux États-Unis.

Sujet		Réponses	Vues
Fatal: could not read Username for 'https://github.com' Self-hosting	10	343	Septembre 3, 2026
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	34	7805	Octobre 22, 2016
40 Fatals and 7 Errors in recent logs Support	12	1806	Février 17, 2017
Locked out of my forum after restore Support	19	647	Janvier 27, 2025
Discourse now stops loading at login dialog when viewed with any browser Self-hosting	21	1512	Janvier 29, 2023

Erreur pour les utilisateurs connectés et blocage de Git

Sujets connexes