Article ID: 121251, created on Apr 22, 2014, last review on Sep 23, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix
  • Plesk 12.5 for Windows


A domain is not loading and a "500 internal server error" is being shown after 45-60 seconds.

The following error can be observed in the domain's /logs/error_log:

[Thu Feb 12 17:07:06 2014] [warn] [client] mod_fcgid: read data timeout in 45 seconds, referer:
[Thu Feb 12 17:07:06 2014] [error] [client] Premature end of script headers: PDF.php, referer:


The following error in /var/log/apache2/error.log:

[Thu Jan 16 08:13:45 2014] [warn] mod_fcgid: process 16576 graceful kill fail, sending SIGKILL


The FcgidIOTimeout value - the maximum period of time the module will wait while trying to read from or write to a FastCGI application - has been exceeded.


  • For Plesk 10.x and 11.0.9 follow these steps:

    Increase the FcgidIOTimeout value in fcgid.conf and restart Apache.

    CentOS: /etc/httpd/conf.d/fcgid.conf

    Debian: /etc/apache2/mods-enabled/fcgid.conf

  • Since Plesk 11.5, according to [Plesk 11.5 Release Notes], ( "title") "FcgidIOTimeout" parameter is set to the same value as max_execution_time php parameter.

    If you face this issue in Plesk 11.5 or 12.x, check this article #127621

Search Words

500 error message

mod_fcgid: read data timeout in 45 seconds

Wrong value of php_handler_type, it can take only FastCGI application

apache resolving to incorrect folder

504 Gateway exim service


Web sites give error 504 Gateway Time-out

mod_fcgid: read data timeout in 45 seconds, referer: htt

high cpu



Websites not loading after the Plesk upgrade

cgi_wrapper/cgi_wrapper(3849) exit(communication error), get signal 7

sending mails over roundcube fails

504, bad gateway

uid: gid: (503/503) cmd: cgi_wrapper

Internal server errors after update


fastcgi causing websites not to load

server locks up




Unable to login webmail

mod_fcgid: read data timeout

High load after upgrade

Internal Server Error

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 742559b1631652fadd74764ae8be475e e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 8b661cab116c79dbe6c4ac5bbdf1c8cb 85a92ca67f2200d36506862eaa6ed6b8 a766cea0c28e23e978fa78ef81918ab8

Email subscription for changes to this article
Save as PDF