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

Resolved 503 error with Plesk 17.8.11 on Debian 9

decanet

Basic Pleskian
Hello,

On a fresh Debian 9, I've installed Plesk 17.8.11 and everything was OK.
But after setup a subscription, I can't access to the website, I've always a 503 error.

I've read A website shows 503 Service Unavailable if PHP-FPM support is enabled on Plesk: AH01079: failed to make connection to backend and tried to restore perms, but I still have the problem.

Something is strange, I have a /var/www/vhosts/system/example.com/php-fpm.sock file but error_log displayed:


[Mon Mar 26 14:01:58.864096 2018] [proxy:error] [pid 21854:tid 140465244444416] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php7-fpm-example.sock (*) failed
[Mon Mar 26 14:01:58.864131 2018] [proxy_fcgi:error] [pid 21854:tid 140465244444416] [client *.*.*.*:38368] AH01079: failed to make connection to backend: httpd-UDS, referer: Example Domain

I've search in all Apache/Nginx/PHP-FPM files, I haven't seen any /var/run/php7-fpm-example.sock reference ?!

I've also tried to switch on FastCGI setting (and not on PHP-FPM), but I still have the same error.

Is it a known problem?

Thank you
 
My bad... The customer was overriding the php-fpm sock path in its .htaccess.

Problem solved!
 
Back
Top