Hello all! I’m off to work, so I’m hoping I’ll be able to find the solution when I get home this afternoon. I updated my calendar app last night and now I’m stuck on this:
What installation method?
This page suggests you’re doing more than just upgrading the Calendar app. 
It suggests your Nextcloud Server itself is being upgraded.
The web Updater is likely disabled because the install method you’re using doesn’t use the internal Updater, but relies on some other mechanism to update. For example, Docker images don’t use the Updater so they tend to turn off. You’ll want to follow the update approach documented for the installation method you chose.
It’s a docker from linuxserver. If I would have known then what I know now, I would have stuck with the official template. Everything is up to date and it was all running fine until I updated my calendar. 
The linux server forums (Procedure to update linuxserver/nextcloud has changed - Docker - openmediavault) state that updates can only be done from inside the image. But everything IS up to date.
Can you post your executed docker-commands with output?
I’m still unclear how you updated the Calendar app and then ended up at the Server update screen. Can you describe precisely how you upgraded Calendar? Are you using something like Watchtower that might have upgraded your Nextcloud image/container as well?
You basically have two mysteries here:
We can suggest some commands that might work, but they won’t solve the mystery and I don’t like telling people to blindly finish an upgrade that wasn’t triggered to start with. 
Please check your Nextcloud Docker container start-up logs. That’s where the upgrade process runs for most Docker images, including the LSIO one you’re using. (In native docker the command would be something like docker compose {container_name} logs at the command line but I’m not sure how much OMV abstracts you away from the native Docker commands).
Also, please check your nextcloud.log for additional clues. There may be something else going on here.
Add’l Refs:
Solution found. Just had to run “occ upgrade” in the docker’s command line.
Yes, I was going to suggest that, but…
It should not have been necessary. Based on what you described yourself doing (updating an app), an upgrade of Nextcloud itself would not have occurred. So I’d still suggest trying to solve that mystery, using some of the previous suggestions, since it may come up again.
Glad you got it working again though!
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.
