Plesk users may notice the error “AH01075: Error dispatching request to” in the domain’s error logs along with a “504 Gateway Time-out” or “503 Service Temporarily Unavailable” error on the website.
As part of our Server Management Services, we assist our customers with several Plesk queries.
Let us today discuss both of these cases differently.
Plesk “AH01075: Error dispatching request to”
Moving ahead, let us see how our Support Techs go about these errors.
503 Service Temporarily Unavailable on Plesk
Symptoms of this error include:
- The /var/www/vhosts/example.com/logs/error_log file shows:
[proxy_fcgi:error] [pid 350:tid 139649016084224] (104)Connection reset by peer: [client 203.0.113.2:58642] AH01075: Error dispatching request to :, referer: http://example.com/wordpress/wp-admin/upload.php
- `dmesg` command output shows:
[4289853.349670] php-cgi[49424]: segfault at 30 ip 00007fc662113088 sp 00007fc630ad3d10 error 4 [4289853.349672] in libMagickCore.so.5.0.0[7fc661f8e000+237000]
An ImageMagick library bug can cause this error.
In order to fix this, we disable the Imagick PHP module for PHP handler for the website:
- To do so, we log in to Plesk
- Browse to Tools & Settings > PHP Settings
- Then click on the PHP handler that is set for the domain, e.g. PHP 5.6:
- To disable the extension, we Uncheck the Imagick checkbox:
Later, we ensure that no sites are using this module.
Later, we ensure that no sites are using this module.Make note that these settings are common to the 5.6.36 CGI applications, 5.6.36 FastCGI applications. The settings apply to all websites that use these handlers.
504 Gateway Time-out on website
Symptoms of this error include:
- Website example.com is not accessible. We come across the below error in a browser:
504 Gateway Time-out
- In the domain error log file, Domains > example.com > Logs, we see the error:
[proxy_fcgi:error] [pid 42290:tid 140458047010560] (70007)The timeout specified has expired: [client 203.0.113.2:54693] AH01075: Error dispatching request to :, referer: http://example.com/gallery
- In the Plesk > Domains > example.com > PHP Settings it shows the website uses a “FastCGI application” (not an “FPM application”) PHP handler.
The cause of this error can be the execution PHP code of the website takes longer than the specified timeout.
To fix the issue, we increase the timeout. We can increase the FastCGI limits for an affected domain only or on a server-wide level.
Increase the FastCGI limits for a single domain:
- Log into Plesk
- Then, go to Domains > example.com > Apache & Nginx Settings.
- We add the following lines to the text boxes Additional directives for HTTP and Additional directives for HTTPS:
FcgidIdleTimeout 1200 FcgidProcessLifeTime 1200 FcgidConnectTimeout 1200 FcgidIOTimeout 1200 Timeout 1200 ProxyTimeout 1200However, if the website still shows “504 Gateway Timeout” we increase timeouts to higher values.
- Finally, we click OK to apply the changes.
Increase the FastCGI limits server-wide:
- We connect to the Plesk server via SSH as the root user.
- Then we open the FastCGI configuration file fcgid.conf in a text editor. The location of the file depends on the operating system:
(a) for CentOS/RHEL/CloudLinux distributions:/etc/httpd/conf.d/fcgid.conf(b) for Debian/Ubuntu distributions:
/etc/apache2/mods-enabled/fcgid.conf - Eventually, we increase FastCGI timeout limits:
FcgidIdleTimeout 1200 FcgidProcessLifeTime 1200 FcgidConnectTimeout 1200 FcgidIOTimeout 1200 - If we use FPM PHP handler to create /etc/httpd/conf.modules.d/00-proxy_timeout.conf then we add the following lines into it:
Timeout 1200 ProxyTimeout 1200 - Then we test configuration with “apachectl configtest” command. The output will be similar to:
# apachectl configtest Syntax OK - Then we restart Apache:
(a) for CentOS/RHEL-based operating systems:# service httpd restart(b) for Debian/Ubuntu-based operating systems:
# service apache2 restart
[Need help with the fix? We’d be happy to assist]
Conclusion
In short, we saw how our Support Techs fix the Plesk error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
my web server reaches the state of being unreachable every 1-2 days until I completely restart the server.
The server is Debian Bullseye with the newest Apache + PHP 7.4. I’m using FPM, because I want to have HTTP2. 16 GB RAM vServer.
/var/log/apache2/error.log:
[Sat May 07 18:01:57.970776 2022] [proxy_fcgi:error] [pid 139033:tid 139719866291968] (70007)The timeout specified has expired: [client xxxIPxxx:47330] AH01075: Error dispatching request to : (polling)
[Sat May 07 18:02:42.854791 2022] [proxy_fcgi:error] [pid 269312:tid 139720560633600] (70007)The timeout specified has expired: [client xxxIPxxx:32702] AH01075: Error dispatching request to : (polling)
Of course, I found different posts / solutions about this issue and I already increased the timeouts for PHP and FPM, but this bug is still there.
/var/log/php7.4-fpm.log:
[07-May-2022 07:05:01] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
[07-May-2022 07:46:42] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
[07-May-2022 09:14:09] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
[07-May-2022 09:27:13] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
[07-May-2022 12:27:16] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
[07-May-2022 15:05:19] NOTICE: [pool www] child 265395 exited with code 0 after 13010.271694 seconds from start
[07-May-2022 15:05:19] NOTICE: [pool www] child 267508 started
[07-May-2022 15:13:40] NOTICE: [pool www] child 265396 exited with code 0 after 13510.447458 seconds from start
[07-May-2022 15:13:40] NOTICE: [pool www] child 267637 started
[07-May-2022 16:13:26] NOTICE: [pool www] child 265945 exited with code 0 after 13622.463297 seconds from start
[07-May-2022 16:13:26] NOTICE: [pool www] child 268279 started
[07-May-2022 17:42:16] NOTICE: [pool www] child 267508 exited with code 0 after 9417.705135 seconds from start
[07-May-2022 17:42:16] NOTICE: [pool www] child 269286 started
[07-May-2022 17:45:07] NOTICE: [pool www] child 267637 exited with code 0 after 9087.193478 seconds from start
[07-May-2022 17:45:07] NOTICE: [pool www] child 269309 started
[07-May-2022 19:20:39] NOTICE: Terminating ...
[07-May-2022 19:20:39] NOTICE: exiting, bye-bye!
[07-May-2022 19:20:55] NOTICE: fpm is running, pid 694
[07-May-2022 19:20:56] NOTICE: ready to handle connections
[07-May-2022 19:20:56] NOTICE: systemd monitor interval set to 10000ms
How can I solve this problem?
Thank you very much.
-
#1
Hi,
when running an intensive php script, I got this error:
Code:
[Fri Oct 24 12:34:51.387882 2014] [proxy_fcgi:error] [pid 10656:tid 140516472919808] (70007)The timeout specified has expired: [client XXXXX58315] AH01075: Error dispatching request to : (polling), referer: http://xxxxx.xxxxx.it/admin/index.php?route=tool/importerHow can I increase this timeout?
-
#2
Try increasing TimeOut in apache configuration, or, if you’d like to have a proxy-specific timeout set, please use ProxyTimeout. Let us know about the results Good luck!
-
#3
Try increasing TimeOut in apache configuration, or, if you’d like to have a proxy-specific timeout set, please use ProxyTimeout. Let us know about the results
Good luck!
I Fixed this problem adding the ProxySet timeout=1800 line in the <Proxy> section of the Virtualhost:
Code:
<Proxy "unix:/usr/local/php55/sockets/ctdev1.sock|fcgi://php-fpm55.ctdev1/">
ProxySet min=0
ProxySet timeout=1800
</Proxy>How can I add the the ProxySet timeout=1800 line via Directadmin so I will not lost it?
-
#4
hi,
I have the same issue, which file I can change value ProxySet timeout?
thanks
-
#5
try setting the Timout option in Apache Configuration
Hey Buddy — Try setting the ProxySet timeout value as 1800 line in the <Proxy> section in the file Virtualhost. That should resolve the issue! Good luck with it and let me know if that works out.
Thanks
Mike from HTML5 Training
-
#6
I updated configs, and now doesn’t work anymore… I’ve again the error:
[proxy_fcgi:error] [pid 19325:tid 140543932651264] (70007)The timeout specified has expired:
What was changed with latest update?
-
#7
Just do the following to set proxy timeout to 1800:
Code:
echo 'ProxyTimeout 1800' >> /etc/httpd/conf/extra/httpd-includes.conf
service httpd restart
That’s it. Please let us know if you still have any questions
-
#8
Just do the following to set proxy timeout to 1800:
Code:
echo 'ProxyTimeout 1800' >> /etc/httpd/conf/extra/httpd-includes.conf service httpd restartThat’s it. Please let us know if you still have any questions
![:)]( "Smile :)")
Worked, thanks!
Содержание
- Issue results are valid but processing is incomplete
- Wikibear
- UFHH01
- Wikibear
- Resolved Problem php-fpm (70007)The timeout specified has expired: AH01075: Er
- sebgonzes
- UFHH01
- sebgonzes
- sebgonzes
- IgorG
- sebgonzes
- Trindex
- sebgonzes
- xernus
- Kingsley
- redcat
- sebgonzes
- lvalics
- sebgonzes
- sebgonzes
- Paddy
- Jonathan H
- Kingsley
- Balanca
- AaronMcH
- PHP-FPM- Error dispatching request to
- James.Simpson
- cPanelMichael
- James.Simpson
- Anoop P Alias
- James.Simpson
- Anoop P Alias
- cPanelMichael
- James.Simpson
- cPanelMichael
- James.Simpson
- cPanelMichael
- Issue (70007)The timeout specified has expired: AH01075: Error dispatching request to :, referer:
- yassi
- Attachments
- IgorG
- yassi
- Bitpalast
- yassi
- Bitpalast
- yassi
- Bitpalast
Issue results are valid but processing is incomplete
Wikibear
Regular Pleskian
I get this on my Ubuntu Webserver from apache this error:
(70008)Partial results are valid but processing is incomplete: AH01075: Error dispatching request to : (reading input brigade)
Any one now to fix this? I think that this maybe has todo with a bad request between php_fpm and mysql server.
UFHH01
Guest
even that the community really likes to help people with issues/errors/problems, you still have to provide essential informations , so that people willing to help you have some facts to investigate:
In YOUR case, you have to provide the following informations:
- YOUR current used Plesk version ( incl. #MU )
- YOUR current used operating system
Wikibear
Regular Pleskian
Sure you are right! Here more information about my system:
Product version: Plesk Onyx 17.0.17 Update #24
Update date: 2017/04/29 19:51
Build date: 2017/03/22 17:00
OS version: Ubuntu 16.04
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2
3. PHP 7.1.4 FPM -> Special Version by Plesk
4.
-rw——- 1 root www-data 375 Apr 29 19:56 httpd.conf
-rw——- 1 root www-data 375 Apr 29 19:56 httpd.conf.bak
-rw——- 1 root www-data 4334 Apr 29 19:56 httpd_ip_default.conf
-rw——- 1 root www-data 4113 Apr 29 19:56 httpd_ip_default.conf.bak
lrwxrwxrwx 1 root root 10 Apr 29 19:56 last_httpd.conf -> httpd.conf
lrwxrwxrwx 1 root root 21 Apr 29 19:56 last_ip_default.conf -> httpd_ip_default.conf
lrwxrwxrwx 1 root root 10 Feb 20 08:14 last_nginx.conf -> nginx.conf
-rw——- 1 root nginx 149 Feb 20 08:14 nginx.conf
-rw——- 1 root nginx 149 Feb 20 08:14 nginx.conf.bak
-rw——- 1 root nginx 2004 Feb 20 08:14 nginx_ip_default.conf
-rw——- 1 root nginx 2004 Feb 20 08:14 nginx_ip_default.conf.bak
-rw-r—r— 1 root root 2 Apr 29 06:25 stat_ttl.conf
-rw-r—r— 1 root root 1 Feb 16 17:51 vhost.conf
-rw-r—r— 1 root root 1 Feb 16 17:51 vhost_ssl.conf
Or you want all files?! For security reasons i feel bad to give my files out to public.
5. No CMS all content on this webspace is developed by myself.
Источник
Resolved Problem php-fpm (70007)The timeout specified has expired: AH01075: Er
sebgonzes
Silver Pleskian
I active 200 domains on one server with php-fpm 5.6, but have several problem :
[Mon Oct 19 17:53:31.969289 2015] [proxy_fcgi:error] [pid 10770:tid 140599495710464] (70007)The timeout specified has expired: [client xx.xx.xx.xx:54335] AH01075: Error dispatching request to :
[Mon Oct 19 17:54:19.939367 2015] [proxy_fcgi:error] [pid 11050:tid 140599462139648] (70007)The timeout specified has expired: [client xx.xx.xx.xx:54542] AH01075: Error dispatching request to :
It seem related to an timeout problem but don’t know for now, how to solve it.
UFHH01
Guest
the default value «Timeout 60» ( 60 seconds ) in your apache — webserver — configuration could be raised at «apache2.conf» or «httpd.conf» ( depending to your system ). Consider to raise it to 180 or 300 seconds.
sebgonzes
Silver Pleskian
I have these with «time» variable :
/etc/httpd/conf.d/fcgid.conf: FcgidIdleTimeout 40
/etc/httpd/conf.d/fcgid.conf: FcgidProcessLifeTime 30
/etc/httpd/conf.d/fcgid.conf: FcgidConnectTimeout 30
/etc/httpd/conf.d/fcgid.conf: FcgidIOTimeout 150
/etc/httpd/conf.d/httpd-includes.conf roxyTimeout 1800 (this one is an test to see if problem solve, but not solve nothing)
I use apache 2.4.6.
sebgonzes
Silver Pleskian
No one have similar problem? we solve it changing all domain from php-fpm to fastcgi, but it’s not seem the best solution.
We found similar problem in other system :
— https://forum.directadmin.com/showthread.php?t=50172
but solution not work for us.
IgorG
Forums Analyst
sebgonzes
Silver Pleskian
Trindex
New Pleskian
sebgonzes
Silver Pleskian
An update of this item. I still have no solution for this problem, I have put all our hosting with fastcgi, but when I test an wordpress website :
— with php 5.6 on fastcgi : 7.7 seg (very bad result)
— with php 5.6 on php-fpm : 2.2s (better result)
— with php 7 on php-fpm : 0.86s (acceptable result)
The problem is that, it’s ok with few website with this php mode, but if I put all 300 domains of server, I will reproduce the problem. Noone have an solution for this error??
xernus
New Pleskian
Kingsley
Silver Pleskian
redcat
New Pleskian
sebgonzes
Silver Pleskian
I never obtain an solution to this problem, in our case that is a litte diferent as your case (webhosting server), only have problem if a large number of domain have php-fpm, if a few number have this version, it’s works.
lvalics
Silver Pleskian
sebgonzes
Silver Pleskian
sebgonzes
Silver Pleskian
Paddy
New Pleskian
I had this error when I copied a site from a different server. My site was still trying to connect to a mysql database on the old server and the connection was blocked. Once I corrected the connection string, all was fine.
Hope this helps someone.
Jonathan H
New Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
Kingsley
Silver Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
Balanca
New Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
AaronMcH
New Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
Thanks for the info, any idea if this can go in the «Additional Apache directives» per domain in Plesk, or does it have to be place in the global config?
In our case this issue doesn’t seem to be consistent, it happened earlier today but only for a few hours and only on one domain, then soon after everything went back to normal, but it seems to be an intermittent issue.
Источник
PHP-FPM- Error dispatching request to
James.Simpson
Member
I am trying everything I can think of to resolve these issues that i keep getting in the error_log
I see these all the time:
I have had a look at all the timeouts and they are all the same (php timeout, apache timeout, all set to 300s)
I’m not sure where to start with this error.
cPanelMichael
Administrator
I recommend searching the PHP-FPM error logs (/opt/cpanel/ea-php$$/root/usr/var/log/php-fpm/error.log) for any domain name’s reaching the max_children limit. You’d replace ea-php$$ with each specific version of PHP (e.g. ea-php70) that PHP-FPM is utilized with on your system. The offending entries will look like this:
If you find specific domain names are reaching the limit, you can increase the max_children value for them using the «Pool Options» feature in «WHM >> MultiPHP Manager».
James.Simpson
Member
I have checked in that file, and there are no errors being displayed at all, just the start up features.
I currently have:
PHP-FPM:
max-children: 100
Process Idle Timeout: 90
Max Requests: 1000
Apache:
Start Servers: 15
Min Spare: 20
Max Spare: 35
Server Limit: 300
Max Request Workers: 200
Keepalive: Off
Keepalive-timeout: 7
Max Keepalive requests: 150
Timeout: 300
Pre VirtualHost Include
Anoop P Alias
Well-Known Member
James.Simpson
Member
Anoop P Alias
Well-Known Member
cPanelMichael
Administrator
You can try increasing both of these values from «300» to a higher number such as «500» to see if the issue continues. Ensure to monitor Apache’s performance after making the change as sometimes a timeout is a good thing since it can prevent Apache from overloading the server.
James.Simpson
Member
I’m not sure if that may be the issue or not — it seems like a sometimes a process may get stuck, as it will wait till 300+ seconds sometimes for a user when they are just trying to load a page, as if somehthing is hogging all the connections? Even though other users can fly through the website without any issues.
I’m struggling to find out what it is at all, as a script shouldnt be running for more than 300 seconds to view a single page?
cPanelMichael
Administrator
You can open a support ticket if you’d like us to take a closer look to rule out any issues with cPanel & WHM itself or it’s integration of PHP-FPM. You can post the ticket number here and we will link this forums thread to the ticket.
James.Simpson
Member
I think it may be server configuration somehwere to be fair.
So what looks like is happening, sometimes when clicking on a link, it will load instantly as it should, but then randomly every now and then, it will just load the page until maximum execution time is hit, and then finally load the page.
So for example just now, i’ve been browsing the website fine, and then i clicked on one link, and it took 290 seconds to load the page. Now after its loaded all the rest of the site is fine again. Not sure what can cause this so randomly — server load isnt massive, and I can see idle processes in apache waiting for a connection. Mysql isnt processing anything either.
cPanelMichael
Administrator
We’d need access to the affected system to reproduce this behavior and determine if there are any obvious reasons for the increased page load time. Are you able to open a support ticket so we can take a closer look?
Источник
Issue (70007)The timeout specified has expired: AH01075: Error dispatching request to :, referer:
yassi
New Pleskian
In the error log I get the following:
(70007)The timeout specified has expired: AH01075: Error dispatching request to :, referer: http://domaine.com/auth/fen Erreur Apache
Already i see this link but nothing always i have this issue,how can i resolved that?
In my config i set application php servi by Apache
thanks in advance
Attachments
IgorG
Forums Analyst
yassi
New Pleskian
thanks for your answer already tested that but always i have the same issue ,so i don’t know why i have one time error apache and other time nginx
FYI I have plesk 12.5.30 linux ubutu 14.04.5 ,version php 5.5.9 ,exécute PHP:Application PHP servi by Apache.
Thanks in advance
Bitpalast
Plesk addicted!
The Nginx error is caused by an unresponsive Apache. Nginx forwards the incoming PHP request to Apache and waits on an answer. Apache does not respond to the request, for that reason Nginx is running into a timeout.
The reason for that Apache is not responding can be too low FPM configuration values as described in the above mentioned KB article, but it can also simply be script errors. If script execution is not finished and no error output (no HTML header) is returned, e.g. if error output is turned off and no page is generated, because script execution failed, the same timeout situation occurs. Normally, this is the main cause for the error.
yassi
New Pleskian
thanks for your answer ,so how can i just use nginx only without apache so i can display my configuration here if you want.
Thanks in advance
Bitpalast
Plesk addicted!
yassi
New Pleskian
Hi, I Have just this in plesk so here screenshot for the plesk configuration 2018 01 12 14 52 58 Param tres PHP pour webonline2018 com Plesk 12 5 30 ;
how can Disable Proxy Mode for Nginx in the Apache/Nginx configuration.
thanks in advance
Bitpalast
Plesk addicted!
This is not the correct page to disable proxy mode. On the PHP page you can only change to «PHP-FPM by Nginx only». Additionally you need to turn of Proxy mode of the Nginx web server.
This is the page you are looking for:
Then disable Proxy mode: 
However, I suppose you think that you can solve your issue by bypassing Apache. Actually, the issue will persist, because your script still will not work properly.
Источник