You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to see the FastCGI increased on some sites to work around the 504 Gateway Timeout error on Nginx with long-running php-fpm scripts.
The applicable PHP directives are already exposed in the PHP panel, but it appears that we need an interface to manage the fastcgi_read_timeout nginx fastcgi directive, presumably under the "Tweaks" menu.
The text was updated successfully, but these errors were encountered:
It occurs to me that client_max_body_size should really be added in addition to fastcgi_read_timeout.
What should really happen here, IMO, is a unified setting for 'Max Upload Size' and 'Script Timeout' that sets the PHP and webserver parameters in tandem with one another:
upload_max_filesize (and possibly post_max_size) PHP directive should match client_max_body_size NGINX directive.
max_execution_time (and possibly max_input_time) PHP directive should match fastcgi_read_timeout NGINX directive.
Sorry, I spoke a bit out of turn. I just realized from your release notes that the FILE UPLOAD SIZE setting takes care of most of this last comment. I'll start a new ticket.
Arrg again. I just realized that this is already completely taken care of with the existing FILE UPLOAD SIZE setting. I was unfortunately looking at the PHP tab instead of tweaks.
I guess that reiterates/further-clarifies the original request to have a SCRIPT TIMEOUT setting in the Tweaks tab, in addition to the FILE UPLOAD SIZE setting.
I'd like to see the FastCGI increased on some sites to work around the 504 Gateway Timeout error on Nginx with long-running php-fpm scripts.
The applicable PHP directives are already exposed in the PHP panel, but it appears that we need an interface to manage the
fastcgi_read_timeout
nginx fastcgi directive, presumably under the "Tweaks" menu.The text was updated successfully, but these errors were encountered: