(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…

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

merefield (Robert) 23. Februar 2023 um 19:06 2

Start with search

This looks similar?

Are you using a totally vanilla standard install?