when i do ./launcher stop app and then ./launcher start app , the site says 502 Bad Gateway . i dont know what is the issue i tried to rebuild but no luck. Please advise how can i fix this.

Could you share the rebuild logs?

root@amsaal:/var/discourse# ./launcher logs app x86_64 arch detected. run-parts: executing /etc/runit/1.d/00-ensure-links run-parts: executing /etc/runit/1.d/00-fix-var-logs run-parts: executing /etc/runit/1.d/01-cleanup-web-pids run-parts: executing /etc/runit/1.d/anacron run-parts: executing /etc/…

That’s not what I meant, could you do ./launcher rebuild app, and then share that output from that? (Also, please put the output in code fences, it makes the topic easier to read)

It would make it a little easier for the user to rebuild it this way as it will log the stdout to a file ./launcher rebuild app >> rebuild.log

if you want different files per rebuild: ./launcher rebuild app > "rebuild-$(date -Imin).log" 2>&1

It takes a minute or two after starting the container for it to start serving stuff. Have you tried waiting a few minutes before going to the web site?

x86_64 arch detected. Ensuring launcher is up to date Launcher is up-to-date Stopping old container app 2.0.20231218-0429: Pulling from discourse/base Digest: sha256:468f70b9bb4c6d0c6c2bbb3efc1a5e12d145eae57bdb6946b7fe5558beb52dc1 Status: Image is up to date for discourse/base:2.0.20231218-0429 dock…

yes so after rebuild process is complete after 30 seconds , the site was not working 502 gateway error then i did /launch restart app with launch start app then it works. so may be there is something happening

That… Feels like an incomplete log. Does it actually end there, or does it just pause for a long period of time? If it’s the second, then you might need more ram/swap.

[Bild] amsaal: yes so after rebuild process is complete after 30 seconds , Try waiting for 60 seconds.

Nginx-Problem, beim Stoppen und Starten der App erhalte ich "502 Bad Gateway"

Produktunterstützung Installation

Firepup650 (Firepup Sixfifty) 16. April 2024 um 10:09 16

Diese können Sie gefahrlos ignorieren, sie hindern Discourse nicht am Wiederaufbau.

Thema		Antworten	Aufrufe
502 bad gateway Self-hosting	4	1074	29. Januar 2024
Brand new install, shows only "502 Bad Gateway" Product Support	2	147	17. März 2025
"502 bad gateway" Nginx Error Self-hosting	3	4345	11. Januar 2017
How to track down failure of discourse upstream inside container resulting in 502 Bad Gateway Self-hosting	7	1310	23. April 2023
Site down: 502 Bad Gateway - after update Self-hosting	2	1241	24. September 2018

Nginx-Problem, beim Stoppen und Starten der App erhalte ich "502 Bad Gateway"

Verwandte Themen