Chris1
Regular Pleskian
Hello,
I am running Plesk 12.5.30 Update #5 on CloudLinux 7.1, all of a sudden today every website on the server started getting a 502 Bad Gateway Nginx error. The Plesk panel itself is fine though, this is loading ok.
I tried restarting nginx and Apache but this didn't help.
I tried re-generating the servers configuration using the "Webserver Configurations Troubleshooter" extension, but this didn't help either.
My last yum updates were these:
I noticed the following error in /var/log/nginx/error.log:
Nothing in the individual vhost error logs that would explain what is going on.
My only way to fix the issue for the time being is to disable nginx.
Any ideas on what is happening here?
I am running Plesk 12.5.30 Update #5 on CloudLinux 7.1, all of a sudden today every website on the server started getting a 502 Bad Gateway Nginx error. The Plesk panel itself is fine though, this is loading ok.
I tried restarting nginx and Apache but this didn't help.
I tried re-generating the servers configuration using the "Webserver Configurations Troubleshooter" extension, but this didn't help either.
My last yum updates were these:
Code:
Oct 11 03:33:08 Updated: psa-php5-configurator-1.7.0-cos7.build1205151001.13.x86_64
Oct 11 03:33:13 Updated: psa-locale-base-en-US-12.5.30-cos7.build1205150929.16.noarch
Oct 11 03:34:02 Updated: plesk-l10n-12.5.30-cos7.build1205150929.16.noarch
Oct 11 03:35:56 Updated: 1:fail2ban-0.9.2-centos7.15093018.noarch
Oct 11 03:35:59 Updated: 1:psa-mod_fcgid-2.0.0-cos7.build1205151001.13.x86_64
I noticed the following error in /var/log/nginx/error.log:
Code:
2015/10/14 12:48:31 [error] 871965#0: *24 connect() failed (111: Connection refused) while connecting to upstream, client: <client_ip>, server: , request: "GET / HTTP/1.1", upstream: "https://<server_ip>:7081/", host: "<server_ip>"
2015/10/14 12:49:26 [alert] 871965#0: *26 open socket #9 left in connection 4
2015/10/14 12:49:26 [alert] 871965#0: aborting
Nothing in the individual vhost error logs that would explain what is going on.
My only way to fix the issue for the time being is to disable nginx.
Any ideas on what is happening here?