• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

nginx: 502 Bad Gateway with every domain change

CGI1979

Basic Pleskian
Hi Plesk friends,

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.

http {

fastcgi_buffers 32 32k;
fastcgi_buffer_size 64k;
fastcgi_read_timeout 600;
fastcgi_send_timeout 600;

}
 
There are many related KB articles. Try to use "502 error" search string there and apply suggested solutions from articles. I hope it will help.
 
Right. Apache graceful restart often helps with this error.
 
Back
Top