-
-
Notifications
You must be signed in to change notification settings - Fork 138
Adjust fastcgi timeout settings in default.conf.sample #525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Increase timeout settings for fastcgi to handle resource-intensive operations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this pull request! Be sure to follow the pull request template!
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
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