• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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