[נפתר] Discourse לא פועל יותר לאחר עדכון ל-2.6.0.beta2

סיכום מבוסס בינה מלאכותית

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.

Hello,

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.

Any ideas how I can start do debug the problem?

Step one would probably be to bypass your socket setup and ascertain what state discourse is in.

502 Bad Gateway

That’s the result if I try to direct access the forum… So something in the background does not run…

I found the problem! It was the bootsnap-compiled-cache directory… There is also another post with this problem…

I found this after I tried to make a backup inside the docker container and got a permission error… Maybe that will help someone else…

How was this instance installed?

How described in the short installation guide.

You followed this guide?

Yes, but this was in spring…

For the new beta i did a update…

git pull
./launcher rebuild app