I got the following error in the logs…
Can’t start Nextcloud because upgrading from 26.0.9.1 to 28.0.0.11 is not supported.
And Nextcloud is just stuck in a rebooting loop. I did a reinstall as well and still getting this error.
Hi @Marky5
Can you please try the following steps:
- SSH into your Umbrel instance
- Run
~/umbrel/scripts/repo checkout https://github.com/getumbrel/umbrel-apps.git - Then run
sudo ~/umbrel/scripts/app restart nextcloud
Please let me know how that goes.
Still stuck in a loop 
I gave it four hours to try and sort itself out now…
nextcloud
Attaching to nextcloud_web_1, nextcloud_cron_1, nextcloud_redis_1, nextcloud_app_proxy_1, nextcloud_db_1, nextcloud_tor_server_1
cron_1 | #30 /var/www/html/lib/private/AppFramework/Utility/SimpleContainer.php(171): OC\Server->OC{closure}(Object(OC\Server))
cron_1 | #31 /var/www/html/3rdparty/pimple/pimple/src/Pimple/Container.php(122): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility{closure}(Object(Pimple\Container))
cron_1 | #32 /var/www/html/lib/private/AppFramework/Utility/SimpleContainer.php(138): Pimple\Container->offsetGet(‘OC\Files\Node\H…’)
cron_1 | #33 /var/www/html/lib/private/ServerContainer.php(171): OC\AppFramework\Utility\SimpleContainer->query(‘OC\Files\Node\H…’, true)
app_proxy_1 | Retrying…
app_proxy_1 | Error wating for port: “The address ‘nextcloud_web_1’ cannot be found”
app_proxy_1 | Retrying…
app_proxy_1 | Error wating for port: “The address ‘nextcloud_web_1’ cannot be found”
app_proxy_1 | Retrying…
app_proxy_1 | Error wating for port: “The address ‘nextcloud_web_1’ cannot be found”
app_proxy_1 | Retrying…
app_proxy_1 | Error wating for port: “The address ‘nextcloud_web_1’ cannot be found”
app_proxy_1 | Retrying…
app_proxy_1 | Error wating for port: “The address ‘nextcloud_web_1’ cannot be found”
cron_1 | #34 /var/www/html/lib/private/AppFramework/Utility/SimpleContainer.php(65): OC\ServerContainer->query(‘OC\Files\Node\H…’)
cron_1 | #35 /var/www/html/lib/private/Server.php(1476): OC\AppFramework\Utility\SimpleContainer->get(‘OC\Files\Node\H…’)
cron_1 | #36 /var/www/html/lib/base.php(629): OC\Server->boot()
cron_1 | #37 /var/www/html/lib/base.php(1171): OC::init()
cron_1 | #38 /var/www/html/cron.php(43): require_once(‘/var/www/html/l…’)
cron_1 | #39 {main}
db_1 | 2023-12-18 17:48:58 0 [ERROR] Plugin ‘Aria’ init function returned error.
db_1 | 2023-12-18 17:48:58 0 [ERROR] Plugin ‘Aria’ registration as a STORAGE ENGINE failed.
db_1 | 2023-12-18 17:48:58 0 [ERROR] InnoDB: The innodb_system data file ‘ibdata1’ must be writable
db_1 | 2023-12-18 17:48:58 0 [ERROR] InnoDB: The innodb_system data file ‘ibdata1’ must be writable
db_1 | 2023-12-18 17:48:58 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
db_1 | 2023-12-18 17:48:58 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
db_1 | 2023-12-18 17:48:58 0 [Note] Plugin ‘FEEDBACK’ is disabled.
db_1 | 2023-12-18 17:48:58 0 [ERROR] Could not open mysql.plugin table: “Unknown storage engine ‘Aria’”. Some plugins may be not loaded
db_1 | 2023-12-18 17:48:58 0 [ERROR] Failed to initialize plugins.
db_1 | 2023-12-18 17:48:58 0 [ERROR] Aborting
redis_1 | 1:C 18 Dec 2023 17:41:52.870 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 18 Dec 2023 17:41:52.879 * monotonic clock: POSIX clock_gettime
redis_1 | 1:M 18 Dec 2023 17:41:52.881 * Running mode=standalone, port=6379.
redis_1 | 1:M 18 Dec 2023 17:41:52.881 # Server initialized
redis_1 | 1:M 18 Dec 2023 17:41:52.881 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
redis_1 | 1:M 18 Dec 2023 17:41:52.890 * Loading RDB produced by version 6.2.2
redis_1 | 1:M 18 Dec 2023 17:41:52.891 * RDB age 91320 seconds
redis_1 | 1:M 18 Dec 2023 17:41:52.891 * RDB memory usage when created 2.25 Mb
redis_1 | 1:M 18 Dec 2023 17:41:52.946 * DB loaded from disk: 0.056 seconds
redis_1 | 1:M 18 Dec 2023 17:41:52.948 * Ready to accept connections
web_1 | Can’t start Nextcloud because upgrading from 26.0.9.1 to 28.0.0.11 is not supported.
web_1 | It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.
web_1 | Configuring Redis as session handler
web_1 | Initializing nextcloud 28.0.0.11 …
web_1 | Can’t start Nextcloud because upgrading from 26.0.9.1 to 28.0.0.11 is not supported.
web_1 | It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.
web_1 | Configuring Redis as session handler
web_1 | Initializing nextcloud 28.0.0.11 …
web_1 | Can’t start Nextcloud because upgrading from 26.0.9.1 to 28.0.0.11 is not supported.
web_1 | It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.
In my case the problem was that, after the update, the web server could no longer connect to the database, it changed from 10.21.21.33 to 10.21.0.70 for some reason.
I was able to fix Nextcloud by:
- Figure out the IP of container
nextcloud_db_1:sudo docker inspect nextcloud_db_1 - Search for
IPAddressand get the value. - Update
dbhostproperty onconfig.phpto new value - Restart nextcloud:
sudo ~/umbrel/scripts/app restart nextcloud
Hope it helps!
Thanks for that. Dug through everything and my IP was still 10.21.21.33 
NextCloud broke after updating to version 28.0.0. I am getting the following:
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.
same error
i still cant get nextcloud to work either it still says i have to upgrade in the toubleshoot logs
Can you describe this in more detail? It’s very confusing that you’re using this thread since Nextcloud is already in version 29.04. is present. You can make an update at any time via the Umbrel Dashboard.
1 Like
Here is what i think the issue is
nextcloud_web_1 | Initializing nextcloud 29.0.4.1 …
nextcloud_web_1 | Can’t start Nextcloud because upgrading from 26.0.9.1 to 29.0.4.1 is not supported.
nextcloud_web_1 | It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.
nextcloud_web_1 | Configuring Redis as session handler
nextcloud_web_1 | Initializing nextcloud 29.0.4.1 …
not sure why its telling me this in the debugger either how do i get it to update properly
You could do manual updates step by step (version to version). I’ve never tried it myself so I don’t know if it works. Some users have described it in this thread:
i have the umbrel home not an RPi anymore so not sure this will work as when i try to open powersehll and ssh into my umbrel it thinks someone is trying to DNS spoof me and im not sure how to proceed from there since it wonbt let me into the umbrel
If I were you, I would simply make a manual backup of your data and reset Umbrel to factory settings. Then you will have fewer headaches. 