• 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.

Resolved Server periodically unavailable or very slow with errors 502/504

Martin589

New Pleskian
Hello,

a virtual server throws error 502 or 504 bad gateway several times a day. When this happens, log in to Plesk is usually possible, but very slow.

In the proxy_error_log of the domain that has the most visitors (and thus is most affected by the problem) I frequently see the following line:

[error] 32214#0: *1062898 upstream timed out (110: Connection timed out) while reading response header from upstream, client: x.x.x.x, server: domain.com, request: "GET /?cat=10 HTTP/2.0", upstream: "fastcgi://unix:///var/www/vhosts/system/domain.com/php-fpm.sock", host: "domain.com"

I have searched and tried various threads on this topic, but nothing seems to help.

Server specs:
Plesk Onyx Version 17.8.11 Update #69
Six cores, 12 GB RAM (10-20% in use)
Approx. ten domains, five of them running Wordpress.

Thanks in advance.

Martin
 
I have searched and tried various threads on this topic, but nothing seems to help.
Contact Plesk Support Team in this case. Experienced supporters will check and fix this issue directly on your server.
 
Or do this while a 504 situation occurs:
# watch "ps aux | sort -nrk 3,3 | head -n 20"
and watch what is causing the high load. It might give you the necessary clue to find out what's going on.
 
Also, use "sensors" to check your cpu temperature. We had a similar problem when a CPU fan was broken. As long as traffic was only normal users, the system ran normally, but when the crawlers hit, the system would slow down and throw all kinds of timeouts.
 
Or do this while a 504 situation occurs:
# watch "ps aux | sort -nrk 3,3 | head -n 20"
and watch what is causing the high load. It might give you the necessary clue to find out what's going on.

I made the following screenshots when the server was working and when it was not (the two right underneath each other, about five minutes apart). Do you have any suggestions what might be wrong?

@IgorG: Can I use the Plesk support for a version of Plesk that I did not licence myself? It was included with the virtual server.

@mow: Since this is a virtual server, I guess I won't be able to check any hardware sensors.
 

Attachments

  • serverprob.jpg
    serverprob.jpg
    529.4 KB · Views: 15
  • serverok.jpg
    serverok.jpg
    269.9 KB · Views: 13
I have the same issue. But this only happens in connection with Roundcube. On the subdomain webmail.mydomain.com I get the following message: 504 Gateway Time-out nginx. The domain www.mydomain.com is not affected.

‪Ubuntu 18.04.3 LTS‬
Plesk Onyx 17.8.11
 
I changed my email setting to Horde and then back to Roundcube. I don't know the reason. At the moment everything looks good. :)
 
The problem was a wrong PHP-FPM configuration. After the optimization the troubles were solved.
 
The problem was a wrong PHP-FPM configuration. After the optimization the troubles were solved.

Can you elaborate on what you did to fix the misconfiguration? We're seeing this too on one of our PHP-FPM servers.
 
Back
Top