Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Plesk “AH01075: Error dispatching request to” – How to fix

by | Jun 3, 2021

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:

  1. To do so, we log in to Plesk
  2. Browse to Tools & Settings > PHP Settings
  3. Then click on the PHP handler that is set for the domain, e.g. PHP 5.6:Plesk AH01075: Error dispatching request to
  4. To disable the extension, we Uncheck the Imagick checkbox:
    Plesk AH01075: Error dispatching request toLater, we ensure that no sites are using this module.

Make note that these settings are common to the 5.6.36 CGI applications5.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:
  1. Log into Plesk
  2. Then, go to Domains > example.com > Apache & Nginx Settings.
  3. 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 1200

    However, if the website still shows “504 Gateway Timeout” we increase timeouts to higher values.

  4. Finally, we click OK to apply the changes.
Increase the FastCGI limits server-wide:
  1. We connect to the Plesk server via SSH as the root user.
  2. 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
  3. Eventually, we increase FastCGI timeout limits:
    FcgidIdleTimeout 1200
    FcgidProcessLifeTime 1200
    FcgidConnectTimeout 1200
    FcgidIOTimeout 1200
  4. 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
  5. Then we test configuration with “apachectl configtest” command. The output will be similar to:
    # apachectl configtest
    Syntax OK
  6. 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";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

GET UP TO 25% OFF

Plesk Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.

GET UP TO 25% OFF

Plesk Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.

Categories:

Tags:

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF