• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Nginx BAD GATEWAY

Is anyone on this thread still experiencing the PHP-FPM issues that result in the NGINX 502 error? If so, can you please let me know if you are running wordpress on your site? Please send me a message. I am very close to solving the issue and can send you some things to try. Thanks!
 
Hello all!

I had a Problem, that i could not send emails to my own domains, because this server running plesk was not the mailserver and probably there was the mailserver enabled.
So I went to Plesk-Panel and uninstalled those Mail-Module-Things I found. http://prntscr.com/2d4sl2

Some Minute later i lost my Panel and there was the plesk 502 Bad Gateway nginx

I still had an opened tab to this uninstall-page.
https://XXXXXXX.stratoserver.net:8447/add_components.html

I found plesk panel and some other things uninstalled too... Why? No idea.
So I added them again. And I had to fill in all the details .. hostname, IP, i had to accept the terms again...

My Users are gone...
My Website still runs...

All those folders plesk created are still there. /var/www/vhosts/... domain1, domain2, domain3
Even the subdomains i routed to this server are known by the apache/nginx ...

I kind of fixt this, but how can I get my configuration back?? I am now frightened to click at something in order not to break my server.
 
i have the same problem
at first i updated mysql to mysql55
then i got mysql.servers dos not exist
when i tried to create database from plesk
i simply used
yum remove mysql55-server mysql55
after removing i used parallels autoinstaller and everything works grate again
with the same admin password and nothing loses :D
if you have installed or upgraded anything just remove
then run the autoinstaller it worked for me on CentOS 5.8 x64!
 
I putted the recommended in the http section in the nginx.conf:

http {
...
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
fastcgi_buffers 8 16k;
fastcgi_buffer_size 32k;

...
}

It worked well.
 
I putted the recommended in the http section in the nginx.conf:

http {
...
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
fastcgi_buffers 8 16k;
fastcgi_buffer_size 32k;

...
}

It worked well.

yes,i think too
 
I see here is 2 type of people on this forum, one whom this tweak is working, and one that isn`t.
I`ve seen this both cases and there are 2 cases for this error.

1. when you get this "upstream" error which is found in error_log, and this error you can easily solve by creating vhost_nginx.conf per domain or putting settings globally in nginx.conf
I`m thinking on this:
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;

but there is also another error which is happening after apache restart which brings us to case
2. When someone add subdomain, domain, or anything on hosting settings via Plesk, Plesk is doing apache restart.
Now in this case Nginx is having a connection to port 7080 which is Apache listening port and as soon Apache is down, boom, 502 bad gateway because there is no more Apache and nginx has no one to serve the request.
As soon apache is UP, F5, and all is up again.

I think that Plesk don`t have to restart apache for new configurations, reload is enough to apply all the settings because the way conf files are generated and included one in each other.

If they could just manage this problem it would be awsome, and I hope that now you will know why someone has problem solved and someone does`t but everyone using Plesk 11.X affected by this 2. problem.
 
Last edited:
Back
Top