I came here hoping to find a step by step diagnostic for when a Discourse site is found in a 502 Bad Gateway condition. It seems the only options are along these lines: Discourse update might have failed, use ./launcher rebuild app. Update and reboot server. These are the kind of responses we get…

[이미지] Tony G: With that info we might learn how to prevent the issue in the future. From reading a lot of posts here, typically forum admins aren’t the cause of 502s, and it’s a plugin/core error. So there wouldn’t be particularly much you could do to avoid those issues. [이미지] Tony G: Wh…

I can open the console on this VPS but the text window is limited. Are there specific logs that can be checked in the container or in the OS? Is there already some form of ping process in the host OS or the container that detects when processes are down? Might a simple server restart within the c…

[이미지] Tony G: I can open the console on this VPS but the text window is limited. I meant browser logs, from dev tools or the equivalent on your browser. [이미지] Tony G: Might a simple server restart within the container be a good way to approach this rather than a full rebuild? I don’t …

Is the disk full? Does this happen frequently? Look at /var/discourse/logs/rails/production.log

Sorry it’s taken so long to get back here… Disk is <50% in use. RAM tends to remain in 80-90 range, Swap <40%. I’m guessing this is where the issue is caused. Logs are in /var/discourse/shared/standalone/log/rails. production.log and related gzipped files have a lot of transaction detail. What m…

[이미지] Firepup Sixfifty: I meant browser logs, from dev tools or the equivalent on your browser. This won’t help. The back end is the issue here. It’s not getting as far as getting a response from the server (hence “bad gateway”) it’s the backend rails logs you need to look at. Try the act…

502 happens when rails doesn’t return a response, usually when the system is booting up or something is misconfigured. You might look in the nginx logs

[이미지] Tony G: “Frequently”? No. But often enough to be mildly annoying and prompt a post here. :slight_smile: I think almost all of the threads here about 502 errors are when Discourse has been upgraded and it hasn’t come back to life. The upgrade failed, or the admin didn’t wait long enough …

Discourse 사이트에서 502 Bad Gateway 오류가 발생했을 때 단계별 진단 방법이 있나요?

제품 지원 자체 호스팅

pfaffman (Jay Pfaffman) 1월 24, 2024, 12:37오전 5

디스크가 가득 찬 것일까요?

이 문제가 자주 발생하나요?

/var/discourse/logs/rails/production.log 파일을 확인해 보세요.

글		댓글	조회수
How to track down failure of discourse upstream inside container resulting in 502 Bad Gateway Self-hosting	7	1300	4월 23, 2023
502 Bad Gateway after updating to latest version Product Support	11	469	4월 29, 2025
Brand new install, shows only "502 Bad Gateway" Product Support	2	142	3월 17, 2025
502 Bad Gateway after Update Product Support	3	957	12월 22, 2018
502 Bad Gateway - Newbie help needed Self-hosting	4	631	11월 15, 2018

Discourse 사이트에서 502 Bad Gateway 오류가 발생했을 때 단계별 진단 방법이 있나요?

Related topics