Welcome! Log In Create A New Profile

Advanced

502 Bad Gateway

Posted by qwertyat 
502 Bad Gateway
July 27, 2016 04:20PM
Hello.

Sometimes I get the "502 Bad Gateway" message. In general I know what this means, but I cannot track any issues down.

I'll start with the setup.

I'm using one root server with multiple containers.
One container is an nginx which is used as a proxy to detect the wanted domain and forward it to an internal ip address.
On the other side I'm using an Apache which hosts a webpage.
A copy of this webpage is also reachable without proxy - this site is running well...

So neither nginx nor apache has some information in the error log.

This message would mean that the apache server cannot be reached.
But It's still up and waiting. Refreshing usually solves the issue.

Maybe someone has a good Idea how to track this issue down?

Thanks in advanced.
I'll provide any asked information as soon as possible.
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 267
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready