How to fix FastCGI timeout issues in Plesk?

27,689

Solution 1

In Plesk 12.x and similar go to Web Server Settings and set the following directives:

Additional directives for HTTP & HTTPS

FcgidBusyTimeout 300
FcgidIOTimeout 250

Above lines will change the timeout for scripts that are quiet too long and take too long to execute.

Additional nginx directives

proxy_read_timeout 300;

Above lines will change the proxy timeout.

If the problem persist, increase the values.

See also: Premature end of script headers: index.php, mod_fcgid: read data timeout


Check the screenshots for the guidance:

Plesk 12.x - Web Server Settings - Additional Apache directives: Additional directives for HTTP & HTTPS - FcgidBusyTimeout & FcgidIOTimeout

Plesk 12.x - Web Server Settings - Additional nginx directives - proxy_read_timeout

Solution 2

A solution provided in the forum of Plesk by Parallels staff

Edit the file:

/etc/httpd/conf.d/fcgid.conf

Specifically, change

FcgidIOTimeout 45

to

FcgidIOTimeout 3600

3600 seconds = 1 hour. Should be long enough for most but adjust upwards if required. I saw one example quoting 7200 seconds in there.

Finally, restart Apache to make the new setting active.

apachectl graceful

Hope it helps

R

Solution 3

My solution to this was to change the PHP settings in the plesk control pannel as per the screenshot.PHP Settings

Share:
27,689
Admin
Author by

Admin

Updated on April 13, 2020

Comments

  • Admin
    Admin about 4 years

    PHP support is currently set to: run as Fast CGI.

    I keep getting these errors in my server log:

    mod_fcgid: read data timeout in 45 seconds

    Premature end of script headers: index.php

    Should be quick fix I think, but I cant find the file to edit. Is this something I can change from Plesk.

    Anyone know how to increase the timeout?

  • SUDO Los Angeles
    SUDO Los Angeles over 10 years
    If I'm not mistaken, he doesn't want to raise timeout but prevent FCGI from timing out.
  • Alex
    Alex over 8 years
    Why don't you provide solution here, in answer? It'd be much more convenient.