• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Bad Gateway 502 every day - PHP process dead!

PARALAX

New Pleskian
Hello!

I'm writing here because our webmaster is obviously not able to solve this problem. Our webserver seems to have strange problems with the current version of Plesk. PHP process will be terminated every day after ~ 20-30 hours completely and permanentely resulting a "Bad Gateway 502" Error. It seems to work again after joining the panel and saving the server configuration again but this can be a permanent solution. I use alltogether 2 domains and 3 other subdomains as website, 4 further as redirection - Nothing unusual. Firewall has been completely disabled for all user and nginx service is completely off (I set it to "Apache & CGI). Nevertheless the HTML-Websites are the only one which are working after the regular crash of "PHP 5.6.13 OS vendor" (result see here). I don't know ehat to do now and think I will leave as customer if he is not able to find out the problem. And I'm very frustrated of the reliability of Plesk up to now in comparison to Confixx which we used before. Can anyone make some suggestions what could be wrong or what's responsible for this?
 
Last edited:
a 502 error means the backend server apache is down, probably due to an overload. Check apache error log in /var/log/httpd/error_log (tail -f /var/log/httpd/error_log)
 
I second the issues described by PARALAX – all latest updates are installed + its a fresh install of Plesk 12.5 on Debian 8 and we rebooted the machine several times. One thing I also came across is duplicate handler entries in Domain PHP settings. Also setting PHP to 5.5 seems just not to work at all (crashes) for projects known to work with PHP 5.5 on other machines.
 
Back
Top