One instance stuck at “Verifying integrity” and one at “Check for expected files”
I have not changed anything in the configuration?
You may try using the command line updater which will display more details.
See Upgrade via built-in updater — Nextcloud latest Administration Manual latest documentation
1 Like
In addition to what @awelzel said:
updater.logwill have more details
Though there should also be more details visible in the web UI too. Not sure why you’re not seeing that. For example, underneath “Check for expected files” it should say Unknown files detected […] then have a bullet point list.
Yes, very useful as you can see:
Instance 1:
2025-05-17T07:00:05+0200 MmqvoMP49o [info] request to updater
2025-05-17T07:00:05+0200 MmqvoMP49o [info] currentStep()
2025-05-17T07:00:05+0200 MmqvoMP49o [info] Step 4 is in state "end".
2025-05-17T07:00:05+0200 MmqvoMP49o [info] POST request for step "5"
2025-05-17T07:00:05+0200 MmqvoMP49o [error] POST request failed with other exception
2025-05-17T07:00:05+0200 MmqvoMP49o [error] Exception: Exception
Instance 2:
2025-05-17T07:02:58+0200 dltIPOXWMo [info] request to updater
2025-05-17T07:02:58+0200 dltIPOXWMo [info] currentStep()
2025-05-17T07:02:58+0200 dltIPOXWMo [info] POST request for step "1"
2025-05-17T07:02:58+0200 dltIPOXWMo [error] POST request failed with other exception
2025-05-17T07:02:58+0200 dltIPOXWMo [error] Exception: Exception
Very strange the whole thing!
Yes you are right, but is was nothing to see there.
In any case, the manual updater on the console solved the problem. It worked straight away.
Lesson learned: Use the manual updater on the console and forget about the GUI.
my own improvisation is to setup an samba-server on the self machine with external hdd (e.g.) to share this an mount in nextcloud. After that to host your date in the share, you will always have access to your data even nextloud crashes. I know, it´s very terrible with this fiasco from nextcloud.
1 Like