Thanks for the tips… the file is not existing so I try several alternatives without more success.
In fact, the point it is not to change locally (for the website who needs) the max_execution_time value ?
How to doing this with php-fpm ?
Hi Hedy, can you please clarify what you changed in your MYSQL file. Is it just that you commented out those two lines or you changed from 1M to 100M for your max_allowed_packet. What about the line of #innodb_use_native_aio?
I’m just curious to know what you changed in MySQL config.
I just migrated several sites over to HestiaCP from VestaCP so I am new to using this fastCGI, which was not in use on previous server. I noticed that all my sites are throwing this timeout error caused by the Wordpress Ewww Image Optimizer plugin.
This is an example of the error, I think it’s the same issue you had, correct?
I see many timeout values listed in the config files for both the Apache2 config (timeout, KeepAliveTimeout), as well as the Nginx config (send_timeout, proxy_connect_timeout, proxy_send_timeout, proxy_read_timeout) files.
And I see a lot of articles with people talking about changing the value if different files. I would like to avoid having to troubleshoot trial and error of changing all these values.
Is it just the basic timeout value specified in the apache config (/etc/apache2/apache2.conf) file that needs to be edited? In my case, by default it’s set to 30 seconds, perhaps I can just try 60 seconds.
# Global configuration
Btw, this post on stackexchange recommends to update to update both Timeout and ProxyTimeout values in the apache config files. however, I don’t see a variable for ProxyTimeout listed. Is this somewhere else, or should I just add that line to this file. You didn’t mention it in your fix, so that’s why I am asking.