I have a site “ forum.6figureswithchris.com ” it was working fine behind a proxy port 8080 and I have apache on port 80 but suddenly it gives “502 bad gateway” ##this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/di…

Solved. It was firewall blocking several processes.

Thanks for the reply. I have tried like 5-6 directives in the domain’s virtualhost in httpd.conf Here are they: Timeout 2400 ProxyTimeout 2400 ProxyBadHeader Ignore ProxyPass / http://0.0.0.0:8080/ retry=1 acquire=3000 timeout=600 Keepalive=On But none of them work

SSH into the host and run a curl http://0.0.0.0:8080. Does that work? (Or 127.0.0.1) If so then I’d quite happily say its something with the proxy directives. Unfortunately I’ve never used Apache as a reverse proxy so I can’t really help you out there.

curl http://0.0.0.0:8080/ gives curl: (56) Recv failure: Connection reset by peer but so does localhost:8080 and 127.0.0.1:8080 I have tried this in httpd.conf same results

Is something blocking loopback connections then? Firewall?

:light_bulb: You’re running CentOS. Is SELinux enabled? That might be blocking Apache from opening connections. Try setsebool -P httpd_can_network_connect to allow Apache to open connections. Check here https://serverfault.com/questions/563872/selinux-allow-httpd-to-connect-to-a-specific-port for …

Thanks again for the input. iptables has no rule for 8080 port ACCEPT or REJECT, netstat tells that tcp6 0 0 :::8080 :::* LISTEN 15160/docker-proxy means docker proxy is 8080 and SELinux is disabled. I checked.

[Bild] itsbhanusharma: How can it be that it works fine on other ports but not on port 80 though? Hmm. Perhaps I misunderstood the OP. [Bild] Aashish_Gangwani: curl http://0.0.0.0:8080/ gives curl: (56) Recv failure: Connection reset by peer but so does localhost:8080 and 127.0.0.1:8080 …

No I have no plugins installed. I checked all logs of discourse carefully there are no errors and it is working on port 8080.

Does Discourse have force_https turned on and apache is trying to access http?

How do I check this? Is there any other config file for discourse?

502 Bad Gateway: Apache-Proxy für Multi-Site-Konfiguration

Produktunterstützung Installation

Thema		Antworten	Aufrufe
Discourse working with jwilder /nginx proxy & acme-companion Self-hosting	6	5724	9. Februar 2022
Discourse not loading with Apache and proxy redirect Self-hosting	7	2628	15. Juli 2020
Set up Discourse on a server with existing Apache sites Sysadmins how-to	16	23221	18. September 2020
I want to install using a reverse proxy for Apache Self-hosting	13	4868	8. August 2021
Fresh install returning 502 Bad Gateway Self-hosting unsupported-install	27	1264	12. März 2024

502 Bad Gateway: Apache-Proxy für Multi-Site-Konfiguration

Verwandte Themen