Server: Updater from 13.0.5 fails on missing target version 14.0.13

[StefanGerl]

Steps to reproduce
Updating Nextcloud from 13.0.5 to 14.0.13 using the web updater
Expected behaviour
The update should run through automatically without errors.

Actual behaviour
Verifying integrity
Download failed - Not Found (HTTP 404) - URL: https://download.nextcloud.com/server/releases/nextcloud-14.0.13.zip

And there really is no file for 14.0.13. I looked into the sources and it seems like the version 14.0.13 is returned by an update server.

[soundzofstatic]

+1 - Same issue here. Upgrading from 13.0.0 to 14.0.13.

I'm trying to figure out what provides the pointer to the newest version available. If we can override that, we can point it to 14.0.12, which does exist.

[soundzofstatic]

I found where the version displayed on /index.php/settings/admin comes from. It's held in the database: oc_appconfig table, held in the lastupdateResult configkey record. However, don't bother changing it to a version where a download exists. Upon clicking on "open updater" it would appear that it phones home and then grabs the latest version anyway, which would then point it back to 14.0.13. Sigh.

[segdy]

+1 :-(

[stevenobird]

Same issue here. Download still missing.

[pjb-mcc]

Same problem exactly. nextcloud-14.0.12.zip file is there but not nextcloud-14.0.13.zip. We should wait for it ?

[StefanGerl]

You could edit the updater/index.php file and hardcode the link to 14.0.12 to the "downloader method", and also add a early return true to the "validation method" which is checking a hash, retrieved from update server, corresponding to 14.0.13, and so will fail otherwise, and than remove that code after update. But that is a really dirty workaround solution.

I guess it is very easy for nextcloud people to fix the "update" server which is returning version 14.0.13 and its hash, to just return the same for 14.0.12?

[StefanGerl]

... or to upload 14.0.13 if it is an existing version. But I guess there would be more bug reports if a official release download is missing on the official download server? I guess its more that the update server returns a wrong version for version 13 updater?

Are all having this issue trying to upgrade from a nextcloud major version 13?

[kesselb]

cc @nextcloud/infrastructure @MorrisJobke

[skerbis]

how can I fix it? ..

[kesselb]

how can I fix it? ..

You can't. For some reason nextcloud 14.0.13 is not uploaded yet but announced by the updater. This might be a technical problem or the update is delayed for some reason (e.g. some problems with instances). I recommend you to postpone the update for the moment.

[skerbis]

What happens when I upgrade manually to 14.0.12 is an update to 15 possible?

... yes

[stevenobird]

how can I fix it? ..

You can't. For some reason nextcloud 14.0.13 is not uploaded yet but announced by the updater. This might be a technical problem or the update is delayed for some reason (e.g. some problems with instances). I recommend you to postpone the update for the moment.

It is uploaded, but in the prereleases folder... https://download.nextcloud.com/server/prereleases/

[anlx-sw]

is there any way to bypass the missing 14.0.13 version and go directly from 13.0.12 to 15.x oder 16.x with the cli updater?

I updated php to 7.3 for another application and now try to get nextcloud running with the newer php version (nc 13 is not supporting php 7.3). as the upgrade process is broken now I can't do that step.

or is there already any eta when the updater problem is fixed? (as the update is not working now for already two days).

[kesselb]

Try the manual upgrade and upgrade to https://download.nextcloud.com/server/releases/nextcloud-14.0.12.tar.bz2. After that you can upgrade to 15 with the updater.

[J-Doc]

@kesselb Unfortunately, it's not that simple. You must edit index.php, use web based updater and force version & signature validation because update from 14.0.12 still try to dl 14.0.13.

[kesselb]

Unfortunately, it's not that simple.

It depends on the selected update channel. Let's assume you're using 14.0.12:

• Update channel production: 14.0.13
• Update channel stable: 15.0.9

[computersalat]

What is the difficulty to publish the missing files on download.nextcloud.com ???
Why not referencing the Updater to make use of the github Release files ??? Would be one Error less.
BTW I do not really see the benefit of having the files away from github on an extra download source ..

[computersalat]

It is uploaded, but in the prereleases folder... https://download.nextcloud.com/server/prereleases/

clever solution :-1:

[stevenobird]

I just got an answer via Twitter from them:

[...] our script which publishes tarballs failed. We will look into that later today and push it. Sorry, this went wrong just before the weekend...

[MorrisJobke]

The files are now in place. Sorry for the inconvenience. Start the updater again and it should properly fetch the files.