How do you increase the apache fastCGI timeout on

Question

Does anybody know how to increase the apache fastCGI timeout on MAMP / MAMP Pro? I've looked everywhere but can't seem to find it.

Any help is appreciated as always.

Thanks, Codarz360

Answer 1

Another solution which worked for me is to simply add

FcgidIOTimeout 3000
FcgidBusyTimeout 3000

directly below MAMP_FastCgiServer_MAMP to the Apache httpd.conf File which can be managed inside MAMP.

Answer 2

I found another solution, which is a less hacky I think.

You can edit MAMP/fcg-bin/phpx.x.x.fcgi and add -idle-timeout 3600 to the exec line.

The result would be like :

exec /Applications/MAMP/bin/php/php5.5.10/bin/php-cgi -c "/Library/Application Support/appsolute/MAMP PRO/conf/php5.5.10.ini" -idle-timeout 3600

That actually works on my setup. Damn you FastCGI timeout error !

Update: For MAMP 4.x, you will need to enable Xdebug in MAMP PHP settings, save, quit MAMP and start it again (via https://stackoverflow.com/a/44341930).

Answer 3

If you're running multiple hosts in MAMP Pro, make sure that you have PHP set to use the “module” option, not the CGI option. Otherwise NONE of the other CGI changes will make any difference. In my instance, setting the suggested -idle-timeout options (detailed above) stopped the server from starting at all.

Answer 4

This was so tedious but finally got it to work.

In MAMP PRO:

Under File > edit template > apache > httpd.conf

Find the block for mod_fcgi

<IfModule mod_fastcgi.c>

and delete the following line:

MAMP_FastCgiServer_MAMP

Since you can specify which version of PHP you want to use with each domain, you need to set a new fastcgiserver, per php version, with its corresponding -idle-timeout ### flag. These should be placed where you deleted the previous MAMP_FastCgiServer_MAMP line.

Examples:

FastCgiServer /Applications/MAMP/fcgi-bin/php5.5.10.fcgi -idle-timeout 2400
FastCgiServer /Applications/MAMP/fcgi-bin/php5.4.25.fcgi -idle-timeout 3600

Save the file and MAMP PRO will require you to restart all of your servers in order for the changes to take place. Test it out and you should be able to do what you where doing with no 500 Errors.