What version of NC were in on and are you trying to upgrade to?
It sounds almost like you somehow ended up with an up-to-date container, but an old NC version that doesn’t support PHP 8.2. Although that error message doesn’t sound quite right either - I suspect it said >=
Did you upgrade the container image first like linuxserver.io recommends:
Actually that approach sounds like it could have issues if one upgrades to the latest container image with a new enough PHP before the installed version of NC supports it…
Yep, the LS folks have an issue open on this. I suspect something got overlooked either in their documented process or some other change in their image… You may want to go add your experience:
So, what is the solution? for unraid user. using the command will not work from the container. I need to update using the Web UI but i can’t access it. I tried maintenance mode but still i can’t get to the Web UI. how do I downgrade my version and prevent auto update? thanks
Nextcloud Updater - version: v25.0.1-4-g5649b58
Current version is 25.0.3.
Update to Nextcloud 25.0.7 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-25.0.7.zip
Open changelog ↗
Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done
Start update? [y/N] y
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Verify integrity
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
Update of code successful.
Should the "occ upgrade" command be executed? [Y/n] y
This version of Nextcloud is not compatible with PHP>=8.2.<br/>You are currently running 8.2.6.
Keep maintenance mode active? [y/N] y
Maintenance mode kept active
Edit the docker. And change the repo to the one listed above. Click apply and it should then update. You’ll likely have to then turn off maintenance mode off before you’ll be able to get back into the web ui after this though.
I’d like some info on this, I got my NC to work again by doing the specific build (246) as stated and was able to update from 24 to 25, but for some reason it will not update to 26, I have to keep battling timeouts and refreshes, then when it gets to the “Extracting” it will go red with the “Parsing Response Failed” then when I click “retry update” it will then just go red without the dropdown, and when I refresh the page it’ll just start from the beginning again.
is the command string you provided just updating the docker container in Unraid, or is it updating the actual docker IN the container?
edit: I finally got it to work/update, I had to use the containers console to command the updates and they finally took, the web ui kept erroring out (red highlights) and having to refresh then restarting the update without actually finishing it.
then I doublechecked by running “a2dismod” to make sure that there were no other versions of php modules loaded other than 8.1 that needed to be disabled.
our choices are: access_compat alias auth_basic auth_digest authn_core authn_file authnz_ldap authz_core authz_host authz_user autoindex cgi cgid deflate dir env filter headers http2 ldap log_debug log_forensic maxminddb mime mime_magic mpm_prefork negotiation php8.1 proxy proxy_fcgi proxy_http proxy_http2 reqtimeout rewrite setenvif socache_shmcb ssl status userdir vhost_alias
Which module(s) do you want to disable (wildcards ok)?
Amazingly the error message still showed up until…
I ran this:
systemctl disable php7.4fpm.service
systemctl start php8.1fpm.service
systemctl restart apache2.service
Hope this helps.