Update fails due to Nginx timeout
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
I've faced this problem for a long time now, but always find a more or less usable workaround.
I have a Nextcloud on a quite slow machine with a large storage.
My files take enough place so Nextcloud updater take a long time to backup.
I first drastically increase timeouts on Nginx settings but now it takes more than an hour just for the backup. I don't want to increase more my timeout settings.
Could your web-based updater periodically send data to keep the connection alive between PHP-FPM et Nginx ?
Now I'm forced to use the command-line updater just for this reason.
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or tests; start by tracing the web-based updater's long-running backup request and its PHP-FPM/Nginx interaction. Done means a lengthy backup keeps the connection alive without requiring higher Nginx timeouts, while the command-line updater remains unnecessary for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100