(Yes, I did search first) After recently using the admin upgrade interface, my discourse instance stopped working, responding with 502 Bad Gateway. I’ve entered the container and it appears to be running an nginx that is expecting a server at localhost:3000, which is not running. (54) Waiting for…

Start with search :wink: This looks similar? [Bild] 502 Bad Gateway after upgrade to 2.7.0beta2 installation Updated from cli: cd /var/discourse git pull ./launcher rebuild app Everything went ok but I got 502 Bad Gateway error. docker ps CONTAINER ID IMAGE …

Given the timing, this is most likely related to a data-explorer change which caused some issues. We’ve now reverted it, so if you try the rebuild again it should work better [Bild] Data explorer taking instance down on rebuild installation I see that has been reverted: …

Yes, I’m using data explorer . I didn’t do a git pull before restarting. When I do a git pull, and then ./launcher restart app it’s not fixed. [Bild] Robert: Are you using a totally vanilla standard install ? Except that I’m running it behind an nginx on the host. (And I have a few plugins, …

[Bild] Godmar Back: I’m now trying ./launcher rebuild app - I hope that rebuilding the app will preserve my forum’s database … and I’m not ending up with my forum reset. Sure, the database is on the mounted shared folder so persists. Restarting the container after a git pull is unlikely to b…

[Bild] Robert: Restarting the container after a git pull is unlikely to be enough. Got it. I also ./launcher rebuild app - would that not pull updates to the plugins?

Yep, that will update the plugins too (so long as they are cloned within app.yml)

In case this is still being investigated I had a 502 gateway error but not directly after the update routine which failed midway with a Ruby versioning error. Since I had not updated the server in about six weeks I ran apt update/upgrade and rebooted. That’s when the 502 error occurred, I could not …

Wie man den Fehler des Discourse-Upstreams im Container aufspürt, der zu 502 Bad Gateway führt

Unterstützung Installation

Thema		Antworten	Aufrufe
502 Bad Gateway after upgrade to 2.7.0beta2 Self-hosting	1	666	19. August 2023
Discourse Install 502 Bad Gateway Self-hosting	8	102	14. Februar 2026
502: Bad Gateway after web update Support	18	5639	15. Januar 2020
Is there a step by step diagnostic for when a Discourse site is found in a 502 Bad Gateway? Self-hosting	8	612	30. März 2024
Brand new install, shows only "502 Bad Gateway" Support	3	70	16. April 2025

Wie man den Fehler des Discourse-Upstreams im Container aufspürt, der zu 502 Bad Gateway führt

Verwandte Themen