Operating system and version (e.g., Ubuntu 24.04):
Debian 12.12
Web server and version (e.g, Apache 2.4.25):
2.4.65
Reverse proxy and version _(e.g. nginx 1.27.2)
none
PHP version (e.g, 8.3):
8.3.26
Is this the first time you’ve seen this error? (Yes / No):
No
When did this problem seem to first start?
This morning
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Just a regular install on shared hosting
Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
Hi, it seems I get very low download speeds here in western Romania, low to the point where the updater always fails. It happens on 2 instances when trying to update to 31.0.10. This is not related to a single IP (I tried from at least 3 IPs, 2 different network setups). And manually downloading from the website gives me a speed of ~40-50Kb/s, with lows in the 10Kb/s which is kind of insane. Especially when it completely stops
Can you please check the server as to what is happening, because this essentially blocks your users? Thanks!
This is a recurring problem. Whenever new versions of NC are released and everyone tries to download them from the download server at the same time, the download speed slows down dramatically. Here in Germany too
sorry for the inconvenience. It was actually the plan to provide the releases from GitHub, but there’s a bug in our update falling back to the old url on our infrastructure.
I assume we will resolve that with the next maintenance release in November and from December on, releases will be downloaded from GitHub.
manually (which took quite a while, but worked flawlessly) and when the automatic updater failed again due to the nasty timeout, I uploaded the installation file via FTP to
cloud / data / updater-xxxxxxxxxxxx / downloads / (your actual path)
Then, in order to prevent the automatic installer to start the download again, I edited the file
.step (one level higher)
and changed
{“state”:“end”,“step”:4}
to
{“state”:“end”,“step”:5}
The trick ist to increment the number of completed steps by one (+1).
Then I started the updater again which caused the updater to use my uploaded installation file instead (without trying to download it once more). And it worked like a charm!
WARNING: If you are not completely shure about what you are doing here, don’t try this at home and just wait for a couple of days before using the automatic installer…
For folks knowing what it is doing are some options available. I just did it by download with wget the nextcloud-31.0.10.tar.bz2 and did the Upgrade manually.
This happens with each update and is reportedly fixed in NC 32. This is because they use a single Hetzner server for everyone, with no CDN. When an update is released, that server becomes saturated.
It also drives me crazy… After 5 years Nextcloud still doesn’t use any form for distributed storage or CDN..
Use Fastly or something, instead of all the traffic going to https://download.nextcloud.com/ from across the world. Downloading with 30 Kbit/s. Come on.
