My nextcloud runs in a docker container and with version 28.0.1 everything was fine for a while.
Then I’ve read that Version 28 has reached EOL and so I’ve planned to upgrade to Version 30.
What I’ve missed was that an upgrade is only possible from one major version to the next, so I should have choosen Version 29.
Now my system is in an undefinite state because if I’ll try to start with version 28 or 29 it says:
nextcloud exited with code 1
nextcloud | Can't start Nextcloud because the version of the data (30.0.4.1) is higher than the docker image version (29.0.10.1) and downgrading is not supported. Are you sure you have pulled the newest image version?
And if I start with version 30 I’m running into several problems with upgrade:
$ docker exec -u www-data nextcloud php occ upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed
Maintenance mode is kept active
Resetting log level
So, anyone any idea how I can get out of this trap without loosing my nextcloud configured as it is (hopefully).
May be there is a simple (database) entry for version 30.0.4 which I could reset and tell the system I’m back in version 29 or something?!
Unfortunately a lot of information to help you is missing as you ignored the required support template. Please edit into your post and add as many information as possible. This will give us the technical info and logs needed to help you!
you will find dozens of similar discussions already tagged multiple_versions for your conveniece
Though I’m surprised you ended up in this state with the v28.0.1 image. There are checks in place that prevent this (which were added back in July 2023 - prior to the release of 28.0.1).
That is, if you’re using the community micro-services Docker image directly. Are you perhaps using a customized image?
My nextcloud runs in a docker container and with version 28.0.1 everything was fine for a while. Then I’ve read that Version 28 has reached EOL and so I’ve planned to upgrade to Version 30.
Not only is v28 EOL, but if you were only running 28.0.1 it means even your v28 deployment was very out of date in and of itself since there were 13 additional maintenance releases published for v28 (28.0.14 was the last). I strongly encourage encourage you to keep fairly up to date on maintenance releases (within whatever supported major version you’re running at all times).
Sorry, you’re absolutely right - I just skipped the template which was not ok.
I’m myself a PHP developer and so I could have imagined how ‘easily’ support can be given without clear technical environment.
You’re right - I’ve missed updates because I’ve tried to solve all other problems around my home network but not the well running nextcloud system - that’s a pity.
I will now skip my “old” nextcloud installation and renamed the basic directory into nextcloud_28 and create a complete new installation with Nextcloud 30 based upon docker compose and re-install the users I need with the same usernames and after that
I will copy back the old data directory content into the new one
Set the owner back to www-data and
try to re-index the new Nextcloud 30 installation
Did I miss anything in your point of view?
I found now way to make my crab nearly-updated installation downgraded to V28 again.
It always runs into problems because of marked Version 30.0.4.1 anywhere.
May be database entries? May be config files?
I’m not sure, but I do not have the time to find out and hoped you would have an idea where to reset.
