Nextcloud error after migration from NS7

[Wellington_Rodrigues]

Hello everyone,
I’ve migrated the Nextcloud, File Server, and Account Provider modules from NS7 to NS8.
The File Server and Account Provider are working properly.

However, with Nextcloud, when I accessed the website for the first time, there was a message saying it needed to be updated. I went to the NS8 Software Center and updated it step by step until the latest version.

After the update, Nextcloud no longer appears in the Apps section (the page is blank), and when I access it via the website, it shows an internal server error.

Some logs from Server

2025-04-06T19:41:48-03:00 [1:nextcloud1:podman]
2025-04-06T19:41:48-03:00 [1:nextcloud1:podman] 2025-04-06 19:41:48.751460396 -0300 -03 m=+0.029895562 container create 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:41:48-03:00 [1:nextcloud1:systemd] Started libpod-30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a.scope - libcrun container.
2025-04-06T19:41:48-03:00 [1:nextcloud1:podman] 2025-04-06 19:41:48.774985368 -0300 -03 m=+0.053420551 container init 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, io.buildah.version=1.33.7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service)
2025-04-06T19:41:48-03:00 [1:nextcloud1:podman] 2025-04-06 19:41:48.778440645 -0300 -03 m=+0.056875820 container start 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:41:48-03:00 [1:nextcloud1:podman] 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a
2025-04-06T19:41:48-03:00 [1:nextcloud1:podman] 2025-04-06 19:41:48.732897312 -0300 -03 m=+0.011332480 image pull  ghcr.io/nethserver/nextcloud-notify_push:1.4.0
2025-04-06T19:41:48-03:00 [1:nextcloud1:systemd] Started nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:42:18-03:00 [1:nextcloud1:nextcloud-notify_push] Error:
2025-04-06T19:42:18-03:00 [1:nextcloud1:nextcloud-notify_push]   × Failed to connect to database: pool timed out while waiting for an open
2025-04-06T19:42:18-03:00 [1:nextcloud1:nextcloud-notify_push]   │ connection
2025-04-06T19:42:18-03:00 [1:nextcloud1:nextcloud-notify_push]   ╰─▶ pool timed out while waiting for an open connection
2025-04-06T19:42:18-03:00 [1:nextcloud1:nextcloud-notify_push]
2025-04-06T19:42:18-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:18.801298772 -0300 -03 m=+0.015501859 container died 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:42:18-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:18.845018969 -0300 -03 m=+0.059222055 container cleanup 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:42:18-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Main process exited, code=exited, status=1/FAILURE
2025-04-06T19:42:18-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:18.896938365 -0300 -03 m=+0.027128149 container remove 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:42:18-03:00 [1:nextcloud1:podman] 30d88e257e41e3e00330bb13d1314423bb107450167c90e1f95faeec32e82c6a
2025-04-06T19:42:18-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Failed with result 'exit-code'.
2025-04-06T19:42:19-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Scheduled restart job, restart counter is at 37.
2025-04-06T19:42:19-03:00 [1:nextcloud1:systemd] Stopped nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:42:19-03:00 [1:nextcloud1:systemd] Starting nextcloud-notify_push.service - Podman nextcloud-notify_push.service...
2025-04-06T19:42:19-03:00 [1:nextcloud1:podman]
2025-04-06T19:42:19-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:19.264929632 -0300 -03 m=+0.030147650 container create 7c4142500286f7f6cd9842090f8fc943a67e188ed4ad6326865e7c54b7c84e21 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:42:19-03:00 [1:nextcloud1:systemd] Started libpod-7c4142500286f7f6cd9842090f8fc943a67e188ed4ad6326865e7c54b7c84e21.scope - libcrun container.
2025-04-06T19:42:19-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:19.288821409 -0300 -03 m=+0.054039421 container init 7c4142500286f7f6cd9842090f8fc943a67e188ed4ad6326865e7c54b7c84e21 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:42:19-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:19.292522885 -0300 -03 m=+0.057740896 container start 7c4142500286f7f6cd9842090f8fc943a67e188ed4ad6326865e7c54b7c84e21 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, io.buildah.version=1.33.7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service)
2025-04-06T19:42:19-03:00 [1:nextcloud1:podman] 7c4142500286f7f6cd9842090f8fc943a67e188ed4ad6326865e7c54b7c84e21
2025-04-06T19:42:19-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:19.246330562 -0300 -03 m=+0.011548574 image pull  ghcr.io/nethserver/nextcloud-notify_push:1.4.0
2025-04-06T19:42:19-03:00 [1:nextcloud1:systemd] Started nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:42:49-03:00 [1:nextcloud1:nextcloud-notify_push] Error:
2025-04-06T19:42:49-03:00 [1:nextcloud1:nextcloud-notify_push]   ╰─▶ pool timed out while waiting for an open connection
2025-04-06T19:42:49-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Failed with result 'exit-code'.
2025-04-06T19:42:49-03:00 [1:nextcloud1:podman] 2025-04-06 19:42:49.749845321 -0300 -03 m=+0.036093350 container create 26a80d84668db13eb8abd280a08bd367cb06e64f37bb0c2550543cc260b3fb6b (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:42:49-03:00 [1:nextcloud1:systemd] Started libpod-26a80d84668db13eb8abd280a08bd367cb06e64f37bb0c2550543cc260b3fb6b.scope - libcrun container.
2025-04-06T19:42:49-03:00 [1:nextcloud1:systemd] Started nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:43:19-03:00 [1:nextcloud1:nextcloud-notify_push] Error:
2025-04-06T19:43:20-03:00 [1:nextcloud1:systemd] Stopped nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:43:20-03:00 [1:nextcloud1:podman]
2025-04-06T19:43:20-03:00 [1:nextcloud1:systemd] Started libpod-74d5eeb6f5f2b1240df0ebd63e2a093c451b611a9cf3b95c1ea57e5f9c087b63.scope - libcrun container.
2025-04-06T19:43:20-03:00 [1:nextcloud1:podman] 2025-04-06 19:43:20.305203963 -0300 -03 m=+0.083501247 container start 74d5eeb6f5f2b1240df0ebd63e2a093c451b611a9cf3b95c1ea57e5f9c087b63 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, io.buildah.version=1.33.7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service)
2025-04-06T19:43:20-03:00 [1:nextcloud1:podman] 74d5eeb6f5f2b1240df0ebd63e2a093c451b611a9cf3b95c1ea57e5f9c087b63
2025-04-06T19:43:50-03:00 [1:nextcloud1:nextcloud-notify_push]   │ connection
2025-04-06T19:43:50-03:00 [1:nextcloud1:nextcloud-notify_push]   ╰─▶ pool timed out while waiting for an open connection
2025-04-06T19:43:50-03:00 [1:nextcloud1:podman] 2025-04-06 19:43:50.380065573 -0300 -03 m=+0.046742296 container cleanup 74d5eeb6f5f2b1240df0ebd63e2a093c451b611a9cf3b95c1ea57e5f9c087b63 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:43:50-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Failed with result 'exit-code'.
2025-04-06T19:43:50-03:00 [1:nextcloud1:podman] 2025-04-06 19:43:50.775448343 -0300 -03 m=+0.057851119 container init ff699b044fde6d8efeb34d8f345cf80c3dc92bf3881fe3badc105b0867588c2f (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, io.buildah.version=1.33.7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service)
2025-04-06T19:43:50-03:00 [1:nextcloud1:systemd] Started nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:44:20-03:00 [1:nextcloud1:nextcloud-notify_push] Error:
2025-04-06T19:44:20-03:00 [1:nextcloud1:nextcloud-notify_push]   × Failed to connect to database: pool timed out while waiting for an open
2025-04-06T19:44:20-03:00 [1:nextcloud1:nextcloud-notify_push]   │ connection
2025-04-06T19:44:20-03:00 [1:nextcloud1:nextcloud-notify_push]   ╰─▶ pool timed out while waiting for an open connection
2025-04-06T19:44:20-03:00 [1:nextcloud1:nextcloud-notify_push]
2025-04-06T19:44:21-03:00 [1:nextcloud1:systemd] Starting nextcloud-notify_push.service - Podman nextcloud-notify_push.service...
2025-04-06T19:44:21-03:00 [1:nextcloud1:podman]
2025-04-06T19:44:21-03:00 [1:nextcloud1:podman] 2025-04-06 19:44:21.596378185 -0300 -03 m=+0.122483608 container create 688cccd52ec9777defe4bd2fc9cad0eb3aeed74ca60b2e361be3d51d7be67620 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, io.buildah.version=1.33.7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service)
2025-04-06T19:44:21-03:00 [1:nextcloud1:systemd] Started libpod-688cccd52ec9777defe4bd2fc9cad0eb3aeed74ca60b2e361be3d51d7be67620.scope - libcrun container.
2025-04-06T19:44:21-03:00 [1:nextcloud1:podman] 2025-04-06 19:44:21.642915946 -0300 -03 m=+0.169021363 container init 688cccd52ec9777defe4bd2fc9cad0eb3aeed74ca60b2e361be3d51d7be67620 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service, io.buildah.version=1.33.7)
2025-04-06T19:44:21-03:00 [1:nextcloud1:podman] 688cccd52ec9777defe4bd2fc9cad0eb3aeed74ca60b2e361be3d51d7be67620
2025-04-06T19:44:21-03:00 [1:nextcloud1:systemd] Started nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:44:51-03:00 [1:nextcloud1:nextcloud-notify_push]   × Failed to connect to database: pool timed out while waiting for an open
2025-04-06T19:44:51-03:00 [1:nextcloud1:nextcloud-notify_push]   ╰─▶ pool timed out while waiting for an open connection
2025-04-06T19:44:51-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Main process exited, code=exited, status=1/FAILURE
2025-04-06T19:44:51-03:00 [1:nextcloud1:podman] 688cccd52ec9777defe4bd2fc9cad0eb3aeed74ca60b2e361be3d51d7be67620
2025-04-06T19:44:51-03:00 [1:nextcloud1:systemd] nextcloud-notify_push.service: Failed with result 'exit-code'.
2025-04-06T19:44:52-03:00 [1:nextcloud1:systemd] Started libpod-9b1eaee3b5db32e20c86d272fc909ea2bfaf9361d81b0fc5fbdd104d6a018b65.scope - libcrun container.
2025-04-06T19:44:52-03:00 [1:nextcloud1:podman] 2025-04-06 19:44:52.325771481 -0300 -03 m=+0.088216797 container start 9b1eaee3b5db32e20c86d272fc909ea2bfaf9361d81b0fc5fbdd104d6a018b65 (image=ghcr.io/nethserver/nextcloud-notify_push:1.4.0, name=nextcloud-notify_push, pod_id=af6fcf2964135be370025e82d208f006f7a825b8b058de119bd661ea9761a6f7, io.buildah.version=1.33.7, PODMAN_SYSTEMD_UNIT=nextcloud-notify_push.service)
2025-04-06T19:44:52-03:00 [1:nextcloud1:podman] 2025-04-06 19:44:52.250125659 -0300 -03 m=+0.012570975 image pull  ghcr.io/nethserver/nextcloud-notify_push:1.4.0
2025-04-06T19:44:52-03:00 [1:nextcloud1:podman] 9b1eaee3b5db32e20c86d272fc909ea2bfaf9361d81b0fc5fbdd104d6a018b65
2025-04-06T19:44:52-03:00 [1:nextcloud1:systemd] Started nextcloud-notify_push.service - Podman nextcloud-notify_push.service.
2025-04-06T19:45:00-03:00 [1:nextcloud1:nextcloud-app] #2 /var/www/html/3rdparty/doctrine/dbal/src/Connection.php(323): Doctrine\DBAL\Connection->detectDatabasePlatform()
2025-04-06T19:45:00-03:00 [1:nextcloud1:nextcloud-app] #7 /var/www/html/lib/private/AppConfig.php(237): OC\AppConfig->loadConfig(false)
2025-04-06T19:45:00-03:00 [1:nextcloud1:nextcloud-app] #10 /var/www/html/lib/private/App/AppManager.php(147): OC\App\AppManager->getInstalledAppsValues()
2025-04-06T19:45:00-03:00 [1:nextcloud1:nextcloud-app] #11 /var/www/html/lib/private/legacy/OC_App.php(191): OC\App\AppManager->getInstalledApps()
2025-04-06T19:45:00-03:00 [1:nextcloud1:nextcloud-app] #13 /var/www/html/lib/base.php(664): OC\AppFramework\Bootstrap\Coordinator->runInitialRegistration()
2025-04-06T19:45:00-03:00 [1:nextcloud1:nextcloud-app] #16 {main}

[mrmarkuz (Markus Neuberger)]

It seems the mariadb database isn’t available.

Does it help to save the NS8 Nextcloud settings in the cluster-admin to reconfigure/restart Nextcloud?

@Wellington_Rodrigues

Failed to connect to database

Please also check the log for mariadb errors.

@Wellington_Rodrigues

However, with Nextcloud, when I accessed the website for the first time, there was a message saying it needed to be updated. I went to the NS8 Software Center and updated it step by step until the latest version.

Did you check if Nextcloud works between the updates?

Let’s check if the database tables can be shown:

runagent -m nextcloud1 podman exec -t nextcloud-db mysql -unextcloud -pnextcloud -D nextcloud -e "show tables;"

[Wellington_Rodrigues]

@mrmarkuz

runagent -m nextcloud1 podman exec -t nextcloud-db mysql -unextcloud -pnextcloud -D nextcloud -e "show tables;"

Error: no container with name or ID “nextcloud-db” found: no such container.

What if I remove the Nextcloud module and migrate it again?
Is that possible, do you know?

[mrmarkuz (Markus Neuberger)]

You could abort the Nextcloud migration and start over. The migration tool will remove the Nextcloud app on NS8 and create a new one.

[Wellington_Rodrigues]

@mrmarkuz

You could abort the Nextcloud migration and start over

The migration was completed successfully. I would have to configure everything again.

Now the Nextcloud information appears in the Apps section.
However, nextcloud-db and nextcloud-redis are showing issues.

[Wellington_Rodrigues]

Migration is no longer possible; it shows a message saying it must be done on another node.

[mrmarkuz (Markus Neuberger)]

@Wellington_Rodrigues

Migration is no longer possible; it shows a message saying it must be done on another node.

Yes, because there’s already an account provider on the node.

@Wellington_Rodrigues

However, nextcloud-db and nextcloud-redis are showing issues.

Maybe it helps to restart the services?

runagent -m nextcloud1 systemctl --user restart nextcloud.service nextcloud-redis.service nextcloud-db.service nextcloud-app.service nextcloud-nginx.service nextcloud-notify_push.service

or

@mrmarkuz

Does it help to save the NS8 Nextcloud settings in the cluster-admin to reconfigure/restart Nextcloud?

As regards nextcloud-redis, you could try to remove the volume as shown here:

Nextcloud won't start after upgrade

Hi all, the latest upgrade broke nextcloud-redis. It won’t start: 2025-04-05T08:44:31-03:00 [1:nextcloud1:nextcloud-notify_push] [2025-04-05 11:44:31.024765 +00:00] ERROR [notify_push] /volume/src/lib.rs:415: Failed to setup redis subscription: Connection refused (os error 111) 2025-04-05T08:44:32-03:00 [1:nextcloud1:nextcloud-notify_push] [2025-04-05 11:44:32.026029 +00:00] ERROR [notify_push] /volume/src/lib.rs:415: Failed to setup redis subscription: Connection refused (os error 111) 2025-…

[Wellington_Rodrigues]

@mrmarkuz

runagent -m nextcloud1 systemctl --user restart nextcloud.service nextcloud-redis.service nextcloud-db.service nextcloud-app.service nextcloud-nginx.service nextcloud-notify_push.service

Great, the services are back to normal, but when I access the website, it’s in maintenance mode.
Is there a way to work around this?

Maintenance mode
This Nextcloud instance is currently in maintenance mode, which may take a while. This page will reload automatically once Nextcloud is available again.

Please contact your system administrator if this message persists or appears unexpectedly.

[mrmarkuz (Markus Neuberger)]

Please try to run occ upgrade and disable maintenance mode manually:

Enter nextcloud1 instance user: (adapt to your nextcloud instance number)

runagent -m nextcloud1

Run occ upgrade:

occ upgrade

Disable maintenance mode:

occ maintenance:mode --off

[Wellington_Rodrigues]

When I run the occ upgrade command, I get the following error:

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
[nextcloud][core][0] {"reqId":"eguFgDFJy8VynWQtwq6k","level":0,"time":"2025-04-07T14:13:11+00:00","remoteAddr":"","user":"--","app":"core","method":"","url":"--","message":"starting upgrade from 27.1.11.3 to 30.0.7.2","userAgent":"--","version":"27.1.11.3","data":{"app":"core"}}
[nextcloud][no app in context][3] {"reqId":"eguFgDFJy8VynWQtwq6k","level":3,"time":"2025-04-07T14:13:11+00:00","remoteAddr":"","user":"--","app":"no app in context","method":"","url":"--","message":"{\"Exception\":\"Exception\",\"Message\":\"Updates between multiple major versions and downgrades are unsupported.\",\"Code\":0,\"Trace\":[{\"file\":\"/var/www/html/lib/private/Updater.php\",\"line\":98,\"function\":\"doUpgrade\",\"class\":\"OC\\\\Updater\",\"type\":\"->\",\"args\":[\"30.0.7.2\",\"27.1.11.3\"]},{\"file\":\"/var/www/html/core/Command/Upgrade.php\",\"line\":190,\"function\":\"upgrade\",\"class\":\"OC\\\\Updater\",\"type\":\"->\",\"args\":[]},{\"file\":\"/var/www/html/3rdparty/symfony/console/Command/Command.php\",\"line\":326,\"function\":\"execute\",\"class\":\"OC\\\\Core\\\\Command\\\\Upgrade\",\"type\":\"->\",\"args\":[{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput\"},{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Output\\\\ConsoleOutput\"}]},{\"file\":\"/var/www/html/3rdparty/symfony/console/Application.php\",\"line\":1078,\"function\":\"run\",\"class\":\"Symfony\\\\Component\\\\Console\\\\Command\\\\Command\",\"type\":\"->\",\"args\":[{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput\"},{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Output\\\\ConsoleOutput\"}]},{\"file\":\"/var/www/html/3rdparty/symfony/console/Application.php\",\"line\":324,\"function\":\"doRunCommand\",\"class\":\"Symfony\\\\Component\\\\Console\\\\Application\",\"type\":\"->\",\"args\":[{\"__class__\":\"OC\\\\Core\\\\Command\\\\Upgrade\"},{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput\"},{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Output\\\\ConsoleOutput\"}]},{\"file\":\"/var/www/html/3rdparty/symfony/console/Application.php\",\"line\":175,\"function\":\"doRun\",\"class\":\"Symfony\\\\Component\\\\Console\\\\Application\",\"type\":\"->\",\"args\":[{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput\"},{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Output\\\\ConsoleOutput\"}]},{\"file\":\"/var/www/html/lib/private/Console/Application.php\",\"line\":183,\"function\":\"run\",\"class\":\"Symfony\\\\Component\\\\Console\\\\Application\",\"type\":\"->\",\"args\":[{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput\"},{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Output\\\\ConsoleOutput\"}]},{\"file\":\"/var/www/html/console.php\",\"line\":87,\"function\":\"run\",\"class\":\"OC\\\\Console\\\\Application\",\"type\":\"->\",\"args\":[{\"__class__\":\"Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput\"}]},{\"file\":\"/var/www/html/occ\",\"line\":33,\"args\":[\"/var/www/html/console.php\"],\"function\":\"require_once\"}],\"File\":\"/var/www/html/lib/private/Updater.php\",\"Line\":199,\"message\":\"Updates between multiple major versions and downgrades are unsupported.\",\"exception\":{},\"CustomMessage\":\"Updates between multiple major versions and downgrades are unsupported.\"}","userAgent":"--","version":"27.1.11.3"}
Exception: Updates between multiple major versions and downgrades are unsupported.
[nextcloud][updater][3] {"reqId":"eguFgDFJy8VynWQtwq6k","level":3,"time":"2025-04-07T14:13:11+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::failure: Exception: Updates between multiple major versions and downgrades are unsupported.","userAgent":"--","version":"27.1.11.3","data":{"app":"updater"}}
Update failed
[nextcloud][updater][3] {"reqId":"eguFgDFJy8VynWQtwq6k","level":3,"time":"2025-04-07T14:13:11+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::updateEnd: Update failed","userAgent":"--","version":"27.1.11.3","data":{"app":"updater"}}
Maintenance mode is kept active
[nextcloud][updater][1] {"reqId":"eguFgDFJy8VynWQtwq6k","level":1,"time":"2025-04-07T14:13:11+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::maintenanceActive: Maintenance mode is kept active","userAgent":"--","version":"27.1.11.3","data":{"app":"updater"}}
Resetting log level
[nextcloud][updater][1] {"reqId":"eguFgDFJy8VynWQtwq6k","level":1,"time":"2025-04-07T14:13:11+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::resetLogLevel: Reset log level to Warning(2)","userAgent":"--","version":"27.1.11.3","data":{"app":"updater"}}

From what I can see, it’s trying to upgrade directly from version 27 to 30, which is not allowed. The upgrade must be done gradually.

Is it possible for me to perform this gradual upgrade?

[mrmarkuz (Markus Neuberger)]

Before upgrading be sure to have a backup.

Enter nextcloud instance:

runagent -m nextcloud1

Edit config.php:

podman unshare nano $(podman volume inspect nextcloud-app-data --format={{.Mountpoint}})/config/config.php

Set version to the current one:

'version' => '30.0.7.2',

Try to upgrade again via occ.

See also Failed update on NS7.9 to NS8 migrated NextCloud - #25 by mrmarkuz

[Wellington_Rodrigues]

Perfect, the commands above solved the issue, but I noticed that my user lost administrator permissions.
Even the admin user no longer has admin rights.
Do you know how to restore those permissions?

[mrmarkuz (Markus Neuberger)]

There’s usually an internal Nextcloud admin with full access and maybe a domain user admin without permissions.

You could enable the internal admin and reset the password to be able to login with full permissions and restore the permissions for administrator.

Admin has no admin privileges in Nextcloud

internal nextcloud user “admin” has all privileges. Domain admins, doesn’t have them by default. runagent -m nextcloud1 occ user:info admin runagent -m nextcloud1 occ user:enable admin runagent -m nextcloud1 occ user:resetpassword admin Replace nextcloud1 with your nextcloud app instance id. On one of the screenshots above I see “builtin administrator user (…” but I believe that user comes from AD/LDAP (you can check it against your domain user’s Display Name or what is between the parenthesi…

[Wellington_Rodrigues]

Thanks again markuz