Adjust fastcgi timeout settings in default.conf.sample #525
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Added some more generous timeouts to the default 60 seconds of nginx mo make possible to process large multipart uploads
Benefits of this PR and context:
In heavy uploads (usually multi GB) and using chunked uploads, the assembling process could take even minutes to end, resulting in a timeout on nginx (504 Gateway Timeout Error) while waiting for a response of php-fpm, this solves the issue.
How Has This Been Tested?
Source / References:
3600 seconds is the default timeout in the official all-in-one next cloud installer