• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Migrating Sites Error

scottthepotter

Basic Pleskian
I have migrated about 40 sites in the past week and today when I go to the 'Migration and Transfer Manager' I get the following error:

Failed to check Plesk API connection to target Plesk server: HttpClientError(HTTP Error 502: Bad Gateway, '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n')

When I check the logs (/var/log/sw-cp-server/error.log) I see the following:
2017/03/01 10:19:21 [error] 30609#0: *66 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 74.208.43.105, server: , request: "POST /enterprise/control/agent.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "localhost"

I have changed the /etc/sw-cp-server/config file to have:
fastcgi_buffers 32 32k;
fastcgi_buffer_size 64k;

I have restarted httpd, nginx, sw-cp-server, sw-cp-engine to no avail

Incidentally when I try to navigate to 'Extensions>Webserver Configurations Troubleshooter' I get a '502 Bad Gateway' error from NGINX.
 
There may be many reasons of this 502 nginx error described in KB articles. I would suggest you use phrase:

failed (104: Connection reset by peer) while reading response header from upstream

for KB search and find there appropriate solution.
 
Back
Top