Gabor H
Basic Pleskian
Hi,
Having issue with Nginx. Websites on the server giving 502 Bad Gateway issue each day, nearly similar time at early morning.
Nginx is up and running. Status is green, enabled.
When I check the error log, I see only these kind of errors. (my IP masked)
2016/09/21 07:41:19 [error] 22856#0: *41591 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.76.81, server: , request: "GET /hundewelt/5013350-trixie-sicherheits-adressanhanger-4-cm-4011905013350.html HTTP/1.1", upstream: "http://XX.X.XXX.XXX:7080/hundewelt/5013350-trixie-sicherheits-adressanhanger-4-cm-4011905013350.html", host: "pfoetchenshop.eu"
Got a new server almost a week ago, with new IP. These GET's could be related to the previous owner of the IP.
But why is Nginx giving the 502 issue only early mornings? Any idea?
Having issue with Nginx. Websites on the server giving 502 Bad Gateway issue each day, nearly similar time at early morning.
Nginx is up and running. Status is green, enabled.
When I check the error log, I see only these kind of errors. (my IP masked)
2016/09/21 07:41:19 [error] 22856#0: *41591 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.76.81, server: , request: "GET /hundewelt/5013350-trixie-sicherheits-adressanhanger-4-cm-4011905013350.html HTTP/1.1", upstream: "http://XX.X.XXX.XXX:7080/hundewelt/5013350-trixie-sicherheits-adressanhanger-4-cm-4011905013350.html", host: "pfoetchenshop.eu"
Got a new server almost a week ago, with new IP. These GET's could be related to the previous owner of the IP.
But why is Nginx giving the 502 issue only early mornings? Any idea?