Site Server timeouts that could cut Backup and Clone processes
The purpose of a server timeout is to prevent a device from endlessly waiting for a sever to respond.
A server connection timeout error does little to tell you what went wrong or why the error happened. It just identifies that the error occurred.
This type of problem may occur if the site server is taking too long to create a backup or a clone of a large site, or simply does not allow enough time for the script to finish.
We have created a list of possible timeouts, and the optimum settings that the timeouts should be increased to, in case the backup or the clone process gets terminated after a certain time.
Nginx:
- proxy_read_timeout = 800
- fastcgi_read_timeout = 800
Apache:
Following settings are very important, and these timeouts should be increased in WHM/cPanel surroundings. Add them if they do not exist within httpd.conf file:
- ProcessLifeTime 7200
- IPCConnectTimeout 800
- IPCCommTimeout 800
If you are using FastCGI module for PHP these are the parameters you should increase:
- FcgidIdleTimeout 800
- FcgidProcessLifeTime 800
- FcgidIOTimeout 800
PHP.ini:
Also all these PHP parameters that can cut the running script:
- max_execution_time = 800
- max_input_time = 800
- memory_limit = 256M
Varnish:
In case your server uses Varnish Caching (usually on managed WordPress hosting servers), you may ask your hosting provider to add following parameters:
- first_byte_timeout=600
- between_bytes_timeout=600
If you encounter a timeout error, or a 500 error that prevents the backup or the clone script from completing, we advise readjusting the aforementioned settings as this has proven to resolve the problem.
We have covered the optimum Site Server Setup that can greatly improve the performance of the Backup and the Clone tool.