• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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"

M

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.
 
You must log in or register to reply here.

Similar threads

A
Issue Website sometime getting down due to nginx & apache error
Replies
3
Views
323
arjch
A
P
Resolved The timeout specified has expired: AH01075: Error dispatching request to : - without URL in my logs - Error 502 - since php 8.2.13 - randomly
Replies
12
Views
14K
phildolyon
P
B
Issue 704710#0: *18394 upstream timed out (110: Connection timed out) while SSL handshaking to upstream
Replies
1
Views
2K
sans
S
W-Bench
Resolved All websites are giving a 504 Timeout when Nginx Proxy is enabled
Replies
15
Views
12K
W-Bench
W-Bench
H
Resolved Best way to develop a website in Plesk is by modifying the host file on my Mac
Replies
7
Views
2K
mow
M
Back
Top