EchoBilisim reported a long, unresponsive wait during a Discourse system update, showing a stalled interface with no progress. pfaffman suggested running cd /var/discourse && ./launcher rebuild app via the server command line. Ed_S added that refreshing the update page might reveal logs, and recommended running git pull before rebuilding to ensure the launcher script is current. After following the advice, EchoBilisim completed the update but encountered a 502 Bad Gateway error upon accessing the site. pfaffman explained that this is normal due to Rails taking longer to start than Nginx, typically resolving within about a minute. EchoBilisim confirmed the issue resolved after waiting, expressing relief and gratitude for the support.
Hello, I like the Discourse system, it wouldn’t have been like this long ago, but now when I say update the system, it says it is updating in the update section, but it does not do anything, I wait for hours because it starts to update, but the update does not start. why does it do this?
As in the screenshot below, it waits and does nothing.
Try logging in the the server and doing
cd /var/discourse
./launcher rebuild app
Sometimes if you refresh that page you will see the logs which should already be visible. Sometimes you’ll see that indeed you need to do a command line update. (git pull is usually done after the cd and before the rebuild, to get an uptodate launcher script.)
Thanks for your help, I did it with the commands you gave, the process is finished, but now when entering the site, it says 502 Bad Gateway, I wonder why it does this?
Ok now thank you very much.
I guess you waited another 63 seconds and the 502 went away? It takes rails a bit more time to start up than it does nginx.
Yes, I was afraid for a moment, that there was a problem, but good luck, thank you very much