Error: copy(https://download.nextcloud.com/server/releases/latest.zip): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests
I don’t know if I’m the only one affected. But every time I upgrade, the download of the new Nextcloud version crashes.
My very simple questions:
Is there a sustainable solution to the problem? How do other users solve the problem? Could it be that the download servers are unsuitable for Nextcloud?
Hey, hm, first time I see that on download.nextcloud.com (saw it a few times on apps.nextcloud.com). Is it one instance you update or multiple?
If you want, you can drop me a PM with your external IP and I can try to check the logs.
Right now I am trying from three different IP addresses in Germany. Via a web interface (Tiny File Manager upload option) I directly get the error message above. On the same system, the normal download during the upgrade stops after about 30 MB, which is probably due to a timeout. On another system via updater.phar it is very slow. The download also takes a very long time via a third IP address. Very long here is greater than 30 minutes. Access is not via a normal DSL connection, but via server systems directly on the Internet. With other new releases, the download was completed in a few seconds, well under a minute.
I also tested it from a forth IP address (DSL) in Germany (wget on Debian desktop) and i get an estimated download time of 30 minutes. Is this normal? I am not a user of Deutsche Telekom where sometimes peering restrictions exists (maybe also to AS24940 Hetzner).
You are welcome to test the download. But it is currently very slow. And unfortunately this happens very often with new releases e.g. now Nextcloud 31.0.1.
I’ll check that. I guess there were a few retries and then you ended up in a 429 then.
This may be the case for 429, as I have made perhaps a maximum of 5 attempts in total on the server of a web host that manages thousands of domains via the same IP address. I wrote you a PN.
But it is already very slow. updater.phar and also wget seem to run through in i think 30 minutes for download. But the webupdater seems to be getting a timeout. That’s really stupid. Not for me. But for other users.
I’m about 20 minutes in, so maybe there is still hope 
Updater run in non-interactive mode.
Start update
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[âś”] Check for expected files
[âś”] Check for write permissions
[âś”] Create backup
[ ] Downloading ...
The download was completed after about an hour. On each individual system, of course. Update with updater.phar works. But i was unable to update the system with the web updater.
I have created the issue #51481. I have suggested a simple solution to what I think is a workaround.
First time struggeling with an update for me…
However: I would propose to serve the files via multiple servers. Nextcloudserver can then only supply checksums.
I’m still in the process. Unfortunately, I killed the process after about 45 minutes, which I probably shouldn’t have done. Now I’m on my second attempt for about as long again. I guess I’ll just wait it out this time…
Oh, and good suggestion btw. 
I forwarded the issue internally already, let’s see.
I got:
No errors in the console log.
The update.log says only:
2025-03-14T12:52:50+0100 lUhGsT6BOD [info] POST request for step "4"
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] startStep("4")
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] downloadUpdate()
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] getUpdateServerResponse()
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] updaterServer: https://updates.nextcloud.com/updater_server/
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] releaseChannel: stable
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] internal version: 31.0.0.18
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] updateURL: https://updates.nextcloud.com/updater_server/?version=31x0x0x18xxxstablexx2025-02-24T21%3A44%3A20%2B00%3A00+051e46a7a272300cf7c90b3e330fd1501fd6a996x8x4x5
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] getUpdateServerResponse response: Array
(
[version] => 31.0.1.2
[versionstring] => Nextcloud 31.0.1
[url] => https://download.nextcloud.com/server/releases/nextcloud-31.0.1.zip
[web] => https://docs.nextcloud.com/server/31/admin_manual/maintenance/upgrade.html
[changes] => https://updates.nextcloud.com/changelog_server/?version=31.0.1
[autoupdater] => 1
[eol] => 0
[signature] => ....
)
2025-03-14T12:52:51+0100 lUhGsT6BOD [info] storage location exists
Manually downloading the zip seems to go VERY SLOWLY (like 40kb/s).
By the way, the update worked for me after all. The second attempt took about an hour, or maybe slightly longer.
If you run the update via CLI, i.e. updater.phar, you have an hour’s time. I even always use tmux on the server side in case the SSH connection between client and server drops. With the webupdater, however, there is usually a timeout after 60 seconds of no real interaction.
Is it bad if the upgrade fails during the downloading part? I just started it, and it’s taking forever. Hopefully, it doesn’t break my installation…
It should not. Only after the succesful download the update starts
Hello,
I had a crash during the downloading via the GUI.
So I have continue through CLI command, and then all the operations has ended successfully (in some minutes only).
It won’t help any of you at the moment (well, unless you download the newer Updater and deploy it manually), but the v32 Updater has download resume + progress logging.
I’d really like to work on Follow redirects to permit distributed downloads via GitHub · Issue #326 · nextcloud/updater · GitHub next (to potentially speed things up / spread the load around GitHub’s infrastructure), but that will require some coordination of changes in the release process.
This is the first time I suffer from this.
Never had performance problems before.
I am no expert, but maybe:
And make it possible that the user can use an own copy of the Nextcloud ZIP see my issue above.
