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:
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
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: 22.214.171.124, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "126.96.36.199: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:
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: 188.8.131.52, 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
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?
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.
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] ....
After upgrading components as suggested by "Tools&Settings->Plesk->Updates and Upgrades" item, components remained the previous version (PHP 5.3.3 and MySQL 5.1.73) as stated by phpinfo() result and by "Tools&Settings->Server Management->Server Components" list, though "Update Components" is no more permitted as if there is nothing more to update.
I need both PHP and MySQL servers updated in order to run Joomla 3.3.6.
Yesterday we upgraded V.11 to V.11.5.30. And now we are not able to restore our backups anymore from our main server on our failover server by CLI (we have automated this with cronjobs and need the CLI backup/restore). We have a failover sulotion with two servers and restore the backups of our main server on our failover server!
If we try to create the map file on our failover server, we get the error:
The dump specification '/home/backups/plesk_partnerserver/dumps/backup_info_1308030132.xml' should be inside of dump directory '/home/backups/plesk/dumps'. /home/backups/plesk_partnerserver/dumps is the path on our failoverserver where we store the backups of our main server and /home/backups/plesk/dumps ist the regular dump path of the failover server.
And if we try to restore the file without creating a map file on our failover server with /usr/local/psa/bin/pleskrestore --restore backup_info_1308030132.xml -level server: Unable to resolve all conflicts
What happend? Now after upgrading to 11.5 our backup- and failover-solutions are in big trouble!
I need to upgrade mysql from 5.1.73 to 5.7 but I have applications like lms, cms, and websites that runs with that version with no problems, my question is: Some of you had problems upgrading mysql, because i kwon plesk runs over mysql y i don't want to mess up with plesk.
We have a plesk server running on a Ubuntu 14.04.2 LTS machine. We check the state of the mailqueue with nagios, executing the "mailq" command. After the AutoInstaller upgraded our installation from 12.0.18 update 38 to 39, we noticed, that the nagios check failed.
After investigating a little bit, it seems that we found the problem:
When I enter "mailq" in the shell, the command is executed and gives me an proper output. But when I try to execute the command with its full path "/usr/bin/mailq" nothing happens, and I have to cancel with [ctrl]+[c]. The which-command delivers exactly the same path as written above...
I am running phpbb 3.0.12 installed from Plesk. In Plesk it is showing me that there is an upgrade available to version 3.1.2-15 however when I Re-Check the version in phpbb it says that I already have the latest version 3.0.12. That's a little weird.
The problem is when I upgrade to 3.1.2-15 in Plesk, it will mess with the whole installation. The forum page will redirect in circles to /install/index.php which doesn't even exist and I can't do anything except revert to before the upgrade.
So my questions are: Why does Plesk show a version 3.1.2-15 but phpbb says the latest one is 3.0.12? How does the upgrade process from Plesk work? I expect it to automatically do everything, or why else would I want to let Plesk upgrade?