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: https://paste.ubuntu.com/p/k7yR42q2vF/

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

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: [immagine] How to Solve 502 Bad Gateway Issues? - KeyCDN Support Having issues with a 502 …

[immagine] 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.

Errore 502 su nginx

Supporto Installazione

Stephen (Stephen) 12 Agosto 2020, 10:32pm 8

Discourse richiede SSD; i normali dischi meccanici non forniscono IOPS sufficienti.

Recommended storage for using Discourse

Argomento		Risposte	Visualizzazioni
Nginx error 502 Self-hosting	6	1124	Agosto 7, 2021
Brand new install, shows only "502 Bad Gateway" Support	3	69	Aprile 16, 2025
502 Bad Gateway after updating to latest version Support	12	259	Aprile 29, 2025
"502 bad gateway" Nginx Error Self-hosting	4	4262	Gennaio 11, 2017
Nginx issue, when i am stop and starting the app getting "502 Bad Gateway" Self-hosting	15	492	Aprile 16, 2024

Errore 502 su nginx

Argomenti correlati