Users reported their Discourse forums went down with error 500 or 504 after attempting an update. Dominique_Dutoit initially sought help after accepting an update email, noting the site promised to recover “later” but offered no timeline. Stephen requested technical details and recategorized the thread to Product Support. Later, Dominique_Dutoit confirmed the forum was restored thanks to pfaffman, who provided guidance on upgrading two-container installations and discouraged avoiding future updates. Multiple users — including Nick_Research, SidV, and Alexandra_Staicu — experienced similar issues, with some resolving them via SSH commands: cd /var/discourse && git pull && ./launcher rebuild app. SidV noted partial category visibility post-rebuild. Alexandra_Staicu still faced 504 errors after rebuilding, and Ed_S pointed to a meta thread for further troubleshooting. The recurring issue suggests a possible bug or configuration sensitivity during upgrades, particularly affecting multi-container setups.
Hi Stephen,
It was the last update, 12 hours ago.
Now, it’s working again. @pfaffman did something and sent a mail.
But I 'm afraid to say that I Have no idea about what to do in a next future…
I suppose that I will not update discourse after this.
Thank you very much Stephen and thank you Jay.
I had the exact same issue and followed advice from @pfaffman on this thread. All you need to do is logon to the server as root and do a pull and rebuild of the app and it will all be fixed:
cd /var/discourse
git pull; ./launcher rebuild app
Of course, the bigger question is why a few of us are having this exact same issue (including the hamburger not working and then the admin page giving a does not exist error) during upgrades when it has never happened before?