This is probably due to your Apache configuration.
The likely reason is the configured timeout, which determines how long the server will complete the process if nothing happens ... it usually makes sense, but when debugging, you can just take a look at something.
My setup is slightly different from yours, but maybe I can help you.
The apache / sites-available folder contains files that configure your virtual hosts associated with the domain. Inside -Tags your domain and protocol I enter
<IfModule mod_fcgid.c> AddHandler fcgid-script .fcgi IdleTimeout 300 IPCConnectTimeout 20 IPCCommTimeout 120 IdleScanInterval 120 </IfModule>
This increased in my case the available period of time until the timeout is started from 40 to 120 seconds.
Then (of course) restart apache.
Maybe this helps.
Raffael
source share