• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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