• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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