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

Input Wrong path: "Website on Plesk server is not accessible: 504 Gateway Time-out: The timeout specified has expired: [client 203.0.113.2:54693] AH01075"

MaRe

New Pleskian
This support article here (Website on Plesk server is not accessible: 504 Gateway Time-out: The timeout specified has expired: [client 203.0.113.2:54693] AH01075: Error dispatching request to) has the wrong path to the config using Debian/Ubuntu. See: Increasing the FastCGI limits server-wide -> 3. "If FPM PHP handler is used create".

The provided path /etc/httpd/conf.modules.d/00-proxy_timeout.conf is only for httpd on CentOS/RHEL/CloudLinux. I think this should be /etc/apache2/apache2.conf for Debian/Ubuntu, right?
 
I recommend creating a new file for Debian/Ubuntu: /etc/apache2/sites-available/00-proxy_timeout.conf
The main one /etc/apache2/apache2.conf could be rewritten during the upgrade.
The author of this KB article will update the information there.
 
Back
Top