• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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