"502 Bad Gateway" on first request in a setup with Apache 2.4-servers as upstreams

Anoop Alias anoopalias01 at gmail.com
Tue Sep 13 10:04:58 UTC 2016

Check the logs of the apache server.

You might need to tweak the proxy_*_timeout settings in nginx , but
usually its the problem with the upstream server that is causing this.
try connecting to the upstream via http://domain:port directly and you
should face the error.

On Tue, Sep 13, 2016 at 3:22 PM, hheiko <nginx-forum at forum.nginx.org> wrote:
> I don't think there is an OS relation on the frontend, the same problem
> occurs with an Centos Nginx as Reverse proxy in front of 3 Apache backends
> on Centos - but it never occurs on windows based Apache backends...
> But we´re on version Lion (http://nginx-win.ecsds.eu)
> Posted at Nginx Forum: https://forum.nginx.org/read.php?2,268306,269511#msg-269511
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Anoop P Alias

More information about the nginx mailing list