Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
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.
Plesk 11.5 - 502 bad gateway
- Thread starter ManuelG2k
- Start date
VinnyT
Regular Pleskian
are you on a WordPress site? If so, what happens if try this:
pick a URL on your site with a permalink. For example www.site.com/about. Instead of using /about/ make sure that there is no / at the end. Do you get an error?
pick a URL on your site with a permalink. For example www.site.com/about. Instead of using /about/ make sure that there is no / at the end. Do you get an error?
I'm still experiencing the exact same problem, even after having installed the latest updates (Plesk 11.5.30 MU#16). I've just increased the buffer sizes in the file "/etc/sw-cp-server/config" to:
fastcgi_buffers 64 64k;
fastcgi_buffer_size 128k;
Restarted both "sw-cp-server" and "sw-engine".
I'm still getting the "502 bad gateway" error randomly when exporting a database. In /var/log/sw-cp-server/error_log:
2013/09/26 09:52:18 [error] 25684#0: *203 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: , request: "POST /domains/databases/phpMyAdmin/export.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "xxx.xxx.xxx:8443", referrer: "https://xxx.xxx.xxx:8443/domains/databases/phpMyAdmin/db_export.php?db=xxx&server=1&token=9c70d142a038d8884a5b73aec7f22552"
fastcgi_buffers 64 64k;
fastcgi_buffer_size 128k;
Restarted both "sw-cp-server" and "sw-engine".
I'm still getting the "502 bad gateway" error randomly when exporting a database. In /var/log/sw-cp-server/error_log:
2013/09/26 09:52:18 [error] 25684#0: *203 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: , request: "POST /domains/databases/phpMyAdmin/export.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "xxx.xxx.xxx:8443", referrer: "https://xxx.xxx.xxx:8443/domains/databases/phpMyAdmin/db_export.php?db=xxx&server=1&token=9c70d142a038d8884a5b73aec7f22552"
StéphanS
Regular Pleskian
VinnyT
Regular Pleskian
Is anyone on this thread still experiencing the PHP-FPM issues that result in the Error 500 or NGINX timeout errors? If so, can you please let me know 1) 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!
VinnyT
Regular Pleskian
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!
any news on that ?
VinnyT
Regular Pleskian
Try this: http://www.curvve.com/blog/servers/2013/fixing-plesk-11-5-error-500-nginx-wordpress-path-url-slash-redirect-error. There are also a few other posts on my blog and forums..
