Can't start Update 27.1.2 to 27.1.3, everything is already green when opening the updater

I’ve got a weird problem. When opening the Updater all marks are already green (web and phar, same on both sides). When starting the update it runs through all points (without doing anything) and throws me back to the Dashboard, without applying the update.

Nextcloud Updater - version: v27.1.0rc3-15-gfa7af53

Current version is 27.1.2.

Update to Nextcloud 27.1.3 available. (channel: “stable”)
Following file will be downloaded automatically:
Open changelog :arrow_upper_right:

Steps that will be executed:
[:heavy_check_mark:] Check for expected files
[:heavy_check_mark:] Check for write permissions
[:heavy_check_mark:] Create backup
[:heavy_check_mark:] Downloading
[:heavy_check_mark:] Verify integrity
[:heavy_check_mark:] Extracting
[:heavy_check_mark:] Enable maintenance mode
[:heavy_check_mark:] Replace entry points
[:heavy_check_mark:] Delete old files
[:heavy_check_mark:] Move new files in place
[:heavy_check_mark:] Done

Continue update? [y/N] y

Update of code successful.

Should the “occ upgrade” command be executed? [Y/n]
Nextcloud is already latest version

Keep maintenance mode active? [y/N]
Maintenance mode already disabled

Maintenance mode is disabled

Running on bookworm, all other updates worked fine so far. It’s not urgent, I think I could update manually or wait for the next release, but maybe there’s an issue somewhere to help.

Thanks and best Regards,

I have also encountered a similar problem,
normally the GUI updater have been quite easy. Also i am updating from 27.1.2 to 27.1.3.
Only different i am running Ubuntu Server 22.04.3 LTS

Arrive until the downloading and then stop there.
get en error due to reverse proxy (i am running behind cloudflare tunnel) and while trying to replicate it now i always get “Step 4 is currently in process. Please reload this page later.”

trying from command line with OCC command the output is the following one,

$ sudo -u www-data php occ upgrade
Nextcloud is already latest version

Am I doing something wrong?
i will monitor closely the conversation to see if anything update.


occ maintenance:repair did the trick for me

Best Regards,

occ upgrade can only be used after the Updater completes. Updater deploys the files (and a bunch of associated tasks) and minimizes interruption to the existing deployment, while occ upgrade deploys the actual changes to your database.

Do you lack outbound connectivity from your NC Server? If so, makes sense this step fails. If not, not sure what’s going on. There is an Updater specific log file created in your data - which will contain more details - located in your configured datadirectory (e.g. /var/www/html/data/) by default.

Makes sense. This does a bunch of things, but the most likely one that helped was the Updater .step folder clean-up. Might have been a stale one from a prior Updater run that didn’t finish. If it re-occurs each update/upgrade cycle, post the contents of your data/updater.log and maybe we can get to the bottom of things.