The user TBauer encountered a 502 Bad Gateway error after updating to Discourse 2.6.0.beta2, despite the Docker container and services running. After troubleshooting, TBauer identified the issue as a permission problem with the bootsnap-compiled-cache directory, discovered while attempting a backup. This aligns with a similar issue discussed in another post. Stephen asked about the installation method, and TBauer confirmed it was initially set up via the short installation guide, with the update performed using git pull and ./launcher rebuild app.
I tried to install the 2.6.0.beta2 update yesterday via SSH. The update itself runs without problems. I also read the information, that the update can take a long time. But after a day, it should work again. I also have a view thousand posts. So it is not a realy large forum…
I also removed all plugins and restarted a rebuild. No change. The Docker container is running. Also the database and also the websocket. But I get a 502 error from the nginx server in front of the docker container.