Hello, I’ve just run ./launcher rebuild app with no apparent errors. But when I try to open the site, I get a 502 error. The nginx error log (shared/standalone/log/var-log/nginx/error.log) shows: 2020/08/12 05:47:43 [error] 653#653: *7 connect() failed (111: Connection refused) while connecting t…

Wooo, looking at the rails logs I found that the unicorn log was huge, complaining about some permission errors. I deleted rm -rf tmp/cache/bootsnap-compile-cache/, and now I see the congratulations screen!!! Thank you friends. I’ll play with this a little more before deciding to recreate it in an …

It shows 502 initially as the services inside the container are starting up. It should go away within 30 seconds. If it doesn’t it is possible that your server’s CPU is under extreme load and it is causing slowdown.

Thanks @itsbhanusharma . I’ve run ./launcher restart app and monitored the load with top, and it’s well under 10%. I think the CPU should be enough to handle the load: $ cat /proc/cpuinfo | grep 'name' | uniq model name : Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz $ cat /proc/cpuinfo | grep …

Which plugins are installed? Is this server on SSD?

I’ve just cloned the repository and run the setup commands, so I guess it just has the default plugins? Not sure where to check, but I’m sure I’ve added none. The server is not SSD.

Hey @elopio Maybe you can post your ‘yml‘ file without any sensitive info?

Sure, it’s here: Ubuntu Pastebin

[이미지] elopio: The server is not SSD. Discourse requires SSD, normal spinning drives don’t deliver sufficient IOPS. [이미지] Which server to choose regarding Discourse requirements? Support You definitely want SSD, the last one seems fine, just check a…

And is that the cause for the 502 error? Or without an SSD should I see the website working, but very slow?

Using a traditional hard drive versus an SSD drive should not cause a 502 error. That’s not really plausible, as your question indicates @elopio . Here is a little writeup which might be helpful: [이미지] How to Solve 502 Bad Gateway Issues? - KeyCDN Support Having issues with a 502 Bad G…

[이미지] neounix: Using a traditional hard drive versus an SSD drive should not cause a 502 error. Speaking from experience slow IO absolutely can and does cause timeouts and a 502 error. SSD-level IOPS are a firm requirement.

nginx에서 502 오류 발생

지원 자체 호스팅

Stephen (Stephen) 8월 12, 2020, 10:32오후 8

Discourse에는 SSD가 필요하며, 일반적인 회전 디스크는 충분한 IOPS를 제공하지 못합니다.

Recommended storage for using Discourse

글		댓글	조회수
Nginx error 502 Self-hosting	6	1233	8월 7, 2021
Brand new install, shows only "502 Bad Gateway" Support	2	139	3월 17, 2025
502 Bad Gateway after updating to latest version Support	11	454	4월 29, 2025
"502 bad gateway" Nginx Error Self-hosting	3	4341	1월 11, 2017
Nginx issue, when i am stop and starting the app getting "502 Bad Gateway" Self-hosting	15	654	4월 16, 2024

nginx에서 502 오류 발생

Related topics