Plesk 12.x / Linux :: Relation 502 Bad Gateway / Can't Apply Process Slot And Restart Iptables
Jul 8, 2015
I have a strange issue on a Plesk 12 VPS. Sometimes the sites result in a "502 Bad Gateway (nginx)". This happens 1 or 2 times a day on different times.
In the httpd log I see a record "can't apply process slot" and in nginx log I see "connect() failed (111: Connection refused) while connecting to upstream" but restarting apache and/or nginx will not always result in a working site.
When I restart iptables everything is working fine again.
I am currently in the process of migrating a few hundred domains from one server to another using Plesk's Migration & Transfer Manager. The servers have the following name servers allocated:
Server 1: ns9.example.com & ns2.example.com Server 2: ns1.example.com & ns2.example.com
In the DNS Zone Template in Tools & Settings on Server 2, can I just click Apply DNS Template Changes and change all migrated domains NS records to ns1/ns2? Will this affect custom DNS entries as a lot of the domains have DNS changes that need to remain. I'm just hoping that this might be a quicker way than going into each domains DNS zone and manually changing ns9 to ns1.
I just really don't want all the domains DNS zones to reset to the standard template on Server 2 ...
Today at 12.50 pm my (ubuntu 14.04.1 LTS) server running plesk 12.0.18 suddenly stopped serving websites. Any attempts to access a webpage on any vhost returned the 502 bad gateway using Nginx error messsage.When I looked at the nginx logs, I found messages like:
Connection refused) while connecting to upstream, client: m.m.m.m, server: , request: "GET /server-status HTTP/1.0", upstream: URL....
Restarting apache & nginx (/etc/init.d/apache2 restart & /etc/init.d/nginx restart) made no difference and I had to reboot to restore http access.
Strangely if I browsed with port 7080 specified (i.e. http://n.n.n.n:7080), this worked fine for all vhosts, so apache (which I believe is listening on this port while nginx listens on port 80) is working fine - nginx is just not able to pass stuff to it?
this is a fresh Plesk 12 installation on a Dedicated Server, on Debian 6. I haven't installed a License key yet.When i tried to run MIgration Manager, the loading was taking forever. Also, when i try to enter Webserver Configurations Troubleshooter, i get 502 Bad Gateway nginx error.In the /var/log/sw-cp-server/error_log i get this error:
Code: 2015/06/17 11:42:47 [error] 3918#0: *52 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: A.B.C.D, server: , request: "GET /modules/configurations-troubleshooter/index.php/index/list HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "X.X.X.X:8443", referrer: "https://X.X.X.X:8443/admin/module/list?context=modules" When i try to insert a Plesk License, i also get this error:
We changed our SSH port (for the slight added security that this offers) and updated our CSF config with the new port so that we can accept connections on this port.
We restarted CSF and we could connect successfully on the new port. When the server is rebooted connections are refused on the port until we *RESTART* CSF then it's all good again.
I would think being that we opened the port in CSF's config that on reboot the port would be opened back up but this is not happening and any time the server is rebooted we have to restart the firewall.
Does anybody have any suggestions on how to "fix" this or at least make it so we don't have to manually restart the firewall?
I shut down iptables on my dedi to try to install Poweradmin but, when the install did not work (probably because DirectAdmin was controlling files and processes I needed for the package) I attempted to restart iptables by running "/etc/init.d/iptables restart" and "service iptables start". It didn't restart. I restarted the webserver running "/etc/init.d/httpd restart". I even rebooted the dedi. Still, no iptables.
After upgrading (i know, i should not do this) from Squeeze to Wheezy i have got a problem with subscriptions.Plesk seems to work, but whein i want do manage a domain/hosting. i just see 502 Bad Gateway nginxClick to expand...
I have upgraded from 11.5 to 12, and now if I try to open Plesk on the port 8443 I have this error:
502 Bad Gateway
nginx
This is the log: 2014/06/27 18:25:13 [crit] 1629#0: *2 connect() to unix:/var/run/sw-engine.sock failed (2: No such file or directory) while connecting to upstream, client: 79.49.206.176, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "87.106.85.233:8443"
Plesk 11.5.30 all latest updated installed is used with Power-User view on an Ubuntu 12.04 LTS 64 Bit system.
The Plesk Interface is working well in general. But if the customer clicks on "Webspaces" -> Add Webspace they run in a:
[URL] ....
Browser: 502 Bad Gateway nginx
To try to fix it with:
/usr/local/psa/admin/bin/nginxmng --disable /usr/local/psa/admin/sbin/httpdmng --reconfigure-all /etc/init.d/apache2 restart /etc/init.d/ngnix restart ( does not work anyway since the customer is not using it ) -> ngnix_enable=no
Which did not work ( ngnix is and was not active )
In the log /var/log/sw-cp-server/error.log
we can see:
[error] 1936#0: *180 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 84.177.142.220, server: , request: "GET /smb/account/create-subscription HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "server:8443", referrer: "https://server:8443/smb/account"
Since we switched to Plesk 12 and activated nginx the problem reoccurs reliably on every domain change. As soon as a customer creates a new domain or alias and Apache restarts nginx delivers 502 errors for maybe 10 seconds. After that everything is fine again.
The system is Debian 6.0.10 with Plesk 12.0.18 Update #38
That might not be a problem in small environments, but with >100 domains the timeout is annoying enough for customers to pick up the phone.
Adding this to /etc/sw-cp-server/config did not do the trick.
We are running Plesk 12 (latest version) on openSuse 13.1. The web server is nginx as a proxy in front of Apache. We are running into a 502 Bad Gateway nginx error when trying to send data from a simple form to a php script.
The log shows: upstream prematurely closed connection while reading response header from upstream
It seems that Plesk does not configure nginx properly as some pages, especially pages that are accessed via https have broken headers. The headers of a page that is displaying
HTTP/1.1 400 Bad Request => Server => nginx Date => Sat, 26 Jul 2014 09:53:13 GMT Content-Type => text/html Content-Length => 166 Connection => close
Today morning a logged in in plesk without problems and started Fail2Ban and closed it. Now I want logged in and get only 502 bad gateway. All Domains working fine and shell access working fine too.
When I turn on nginx for the server I am able to browse non SSL protected sites correctly. I receive a 502 Bad Gateway error on any sites that have an SSL certificate. Is there a fix for this? I have been unable to find one.
under Plesk 12.0.18 PHPMyAdmin is failing to import a 3 MB SQL dump of a simple Joomla website. "Error 505 Bad Gateway", it says.It happens with other dumps too, some as small as ~500 KB. The format (SQL or ZIP) of the file uploaded doesn't seem to matter, because the upload itself seems to work; it seems it's the post-processing what is raising the error.
The funny thing is that the import itself seems to work (the contents of the SQL dump are imported), but the error message appears and causes confusion and support requests from our clients./var/log/sw-cp-server/error_log says:
2015/05/15 03:19:31 [error] 10215#0: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: XX.XX. XXX. XXX, server: , request: "POST /domains/databases/phpMyAdmin/import.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "xxxx. xxxxxxx.com:8443", referrer: URL.....To me it sounds like a timeout.
This seems to be a "popular" error among Plesk users, and I have tried this, this and this with no luck.
As I read, when Plesk and WHMCS are in the same server, you may have 502 bad gateway errors when creating an account through WHMCS..Page not Found/Timeout/502 Bad Gateway error creating accounts with Plesk 10+..By default Plesk 10 and above performs a forced restart of apache when an account is created or suspended which causes WHMCS to lose connection to the server, and if your WHMCS is on the same server, you will also lose connection to WHMCS at the same time.
In order to resolve this please refer to the following knowledgebase article for instructions on configuring Plesk to perform a graceful restart instead: URL..
But when I activate nginx in Plesk the 502 bad Gateway problem comes back.Is there an option to activate Nginx graceful restart in Plesk?
We found 502 Bad Gateway error Nginx on multiple domain "currently troissoeursetunfrere.com is a wordpress site e-commerce" and also malittleboutique.com ecommerce wordpress, possibly to fix this problem we have followed this tutorial " [URL] ....
I'm migrating 11 domains from my old server to my new server, and it's been running now for 3 hours and the progress section shows 100% but it looks like it's still running.
And each time I check the "Domains" section I see a couple of my domains listed but not all of them yet, and the ones I do see the "Disk Usage" on one of my domains that I know is large shows the same figure each time I go to this page; it doesn't seem like it has increased at all.
How can I tell if the migration is still processing or if it has froze and I should restart the migration again?
I have a list of bad Ips and would like to add it into iptables, but I don't went to enter one-by-one or by command line, I would like to insert into list file of iptables editing a file or something like that, where and how I can procedure to do this?
