You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] This version of Nextcloud is not compatible with PHP>=8.2. #313
After Update commit c07466d yesterday Nextcloud only shows:
This version of Nextcloud is not compatible with PHP>=8.2.
You are currently running 8.2.6.
I did the steps from pinned Issue but it changed nothing. Going back to 26.0.2-ls246 works for me. But with Change 26.0.2-ls247 and php 8.2 it won't work anymore for me even if I update the install as explained.
Expected Behavior
No response
Steps To Reproduce
Use latest Image
Environment
- OS:Unraid- How docker service was installed:
CPU architecture
x86-64
Docker creation
Unraid Community Apps
Container logs
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] done
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 99
User GID: 100
───────────────────────────────────────
using keys found in /config/keys
**** The following site-confs have extensions other than .conf ******** This may be due to user customization. ******** You should review the files and rename them to use the .conf extension or remove them. ******** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default.bak
/config/nginx/site-confs/default.conf.bak
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Reacted by Brennen Heinrich, Peter Gerhards, Jarbas Peixoto Júnior, Pavel Peřina, Nathan Friedly, Amity, Enlinks, Matthew Conto, markgllin, Connor Fonte and 3 more
seems from 25 to 26 is not a auto update at this point. I did go back to 26.0.2-ls246 and updated via settings UI and go back to latest image works. But I guess 25 is still long term stable release from nextcloud and it won't work with php 8.2
Just to chime in. I am having the same issue. Like paskalll I run the manual update from the server "docker exec -it nextcloud updater.phar" and the latest it takes me to is 25.0.7. It seems 26 was released but the updater is not seeing it? Is the easiest way to fix this just to go back to an older docker image?
Yes it's supported within our container, it's the update process we recommend in our readme.
The tags are for what version is included for a new install. For exisiting installs, you need to make sure you're on a newer tag for the correct dependencies.
The container doesn't update nextcloud automatically when you updated the container image. Updates to nextcloud are done manually.
I am in the process of building nextcloud into the container. Builds that should work are ready, but need more testing than just me. I haven't asked for user testing at this point because testing requires a well planned backup and restore procedure, which is something we advise everyone have in general. If testing is successful, this build could eventually replace our current builds, and it would replace the current manual upgrade process. Tldr: the test builds could break your install in an unrecoverable way.
If I attempt to run the updater when on tag 26.0.2 and 26.0.2-247, I receive this: The updater loops infinitely like so, and upgrading to version 26 is impossible. And occ upgrade can't be run after the update.
Nextcloud Updater - version: v25.0.3-2-gd49ee0d
Current version is 25.0.7.
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 ↗
However, if I try to run the upgrader on tag 26.0.2-ls246 like people are recommending, I get told:
Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused in /config/www/nextcloud/lib/private/DB/Connection.php:139
I'm using MariaDB as my database. What should I attempt from here?
Edit: Resolved, My MariaDB instance was unavailable due to an incorrect shutdown, and was updated before rebooting. This caused it to fail to launch properly.
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
Continue 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
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done
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. You are currently running 8.2.7.`
FINALLY got the update to 26.x.x to work, being new to all this stuff i had to first figure out WHERE to try running these commands. I had to open the containers console (terminal) and run the command "updater.phar" there, no clue where to use "docker exec -it nextcloud updater.phar" as it didn't work in the containers terminal/console window (maybe Unraid terminal window?!). after it finally taking 26 i removed the version tag on the repo line and it works correctly, currently trying to update to 27.x.x (and beyond) the same way, hope it works (knock on wood).
too bad there isn't a way to have the internals of the container to auto-update, or is there and I'm missing something?
Don't know why this issue is closed, it should not be.
Just ran into the issue, too. We are on stable channel, nextcloud version 25.0.10, non-docker installation. We do not want to switch to a beta channel for production software.
Activity
github-actions commentedon Jun 1, 2023
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
aptalca commentedon Jun 1, 2023
What version is your nextcloud? You need to keep updating as long as it lets you. It does incremental updates.
ps-kl commentedon Jun 1, 2023
25.0.7 and the support for php 8.2 comes with 26 so I have to change to 26.0.2.
docker exec -it nextcloud updater.phar
Nextcloud Updater - version: v25.0.3-2-gd49ee0d
Current version is 25.0.7.
No update available.
Nothing to do.
seems from 25 to 26 is not a auto update at this point. I did go back to 26.0.2-ls246 and updated via settings UI and go back to latest image works. But I guess 25 is still long term stable release from nextcloud and it won't work with php 8.2
tstrausbaugh-dev commentedon Jun 1, 2023
Just to chime in. I am having the same issue. Like paskalll I run the manual update from the server "docker exec -it nextcloud updater.phar" and the latest it takes me to is 25.0.7. It seems 26 was released but the updater is not seeing it? Is the easiest way to fix this just to go back to an older docker image?
Biepa commentedon Jun 1, 2023
Going back to "26.0.2-ls246" like @paskalll mentioned atleast let me use nextcloud again.
ps-kl commentedon Jun 1, 2023
Done
An4cl3t0 commentedon Jun 1, 2023
Same for me, " This version of Nextcloud is not compatible with PHP>=8.2."
j0nnymoe commentedon Jun 1, 2023
@An4cl3t0 then read the comments above you. It's already well documented what to do.
kvn1351 commentedon Jun 1, 2023
If only they had a "stable" tag :/
j0nnymoe commentedon Jun 1, 2023
Or just don't use latest and pin to an actual version tag. If you just run with using
:latest- you're always running the risk. https://www.linuxserver.io/blog/2018-04-22-the-dangers-of-pulling-latestThe reason so many people are experiencing this issue is due to
Our nextcloud has always been like this and it's documented in our readme.
peterge1998 commentedon Jun 1, 2023
Maintenance mode is active after starting with this tag...
Edit:
Fixed it by docker exec -it nextcloud updater.phar
I am coninuing to use latest & watchtower.
jarbelix commentedon Jun 1, 2023
https://github.com/linuxserver/docker-nextcloud#:~:text=Simply%20pulling%20lscr.io/linuxserver/nextcloud%3Alatest%20should%20retrieve%20the%20correct%20image
This time it didn't work out so well.
jarbelix commentedon Jun 1, 2023
Sema for me: https://nextcloud.tiozaodolinux.com/
This environment is a test environment. I'll leave it until the fix comes out.
18 remaining items
Beryllium30 commentedon Jun 10, 2023
Hey
I am a bit confused and not sure how to progress :D
I basically changed the tag in Unraid to:
lscr.io/linuxserver/nextcloud:26.0.2-ls246Nextcloud works again then and I wanted to update to the 26 version.
If I go to the docker terminal and use: updater.phar i get the following message:
`Nextcloud Updater - version: v25.0.3-2-gd49ee0d
Current version is 25.0.4.
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 ↗`
Why can't I update to the 26 version? Super confused also about the version discrepancy from the tags.
Would appreciate any help!
BR
Berry
j0nnymoe commentedon Jun 10, 2023
You have to run the updater multiple times, You can't just jump to the latest version.
Beryllium30 commentedon Jun 10, 2023
Is that supported with the docker container?
but why is there a version missmatch?
j0nnymoe commentedon Jun 10, 2023
Yes it's supported within our container, it's the update process we recommend in our readme.
The tags are for what version is included for a new install. For exisiting installs, you need to make sure you're on a newer tag for the correct dependencies.
nemchik commentedon Jun 10, 2023
The container doesn't update nextcloud automatically when you updated the container image. Updates to nextcloud are done manually.
I am in the process of building nextcloud into the container. Builds that should work are ready, but need more testing than just me. I haven't asked for user testing at this point because testing requires a well planned backup and restore procedure, which is something we advise everyone have in general. If testing is successful, this build could eventually replace our current builds, and it would replace the current manual upgrade process. Tldr: the test builds could break your install in an unrecoverable way.
Wigsinator commentedon Jun 11, 2023
If I attempt to run the updater when on tag 26.0.2 and 26.0.2-247, I receive this: The updater loops infinitely like so, and upgrading to version 26 is impossible. And occ upgrade can't be run after the update.
However, if I try to run the upgrader on tag 26.0.2-ls246 like people are recommending, I get told:
Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused in /config/www/nextcloud/lib/private/DB/Connection.php:139I'm using MariaDB as my database. What should I attempt from here?
Edit: Resolved, My MariaDB instance was unavailable due to an incorrect shutdown, and was updated before rebooting. This caused it to fail to launch properly.
doreks commentedon Jun 20, 2023
hi @j0nnymoe
same issue here:
and here the log after try to upgrade manually:
`root@d2b6296cfc12:/#updater.phar
Nextcloud Updater - version: v25.0.3-2-gd49ee0d
Current version is 25.0.7.
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
Continue 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
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done
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.
You are currently running 8.2.7.`
any way to fix it and can work normally?
thanks for the support!
nemchik commentedon Jun 20, 2023
#288 has all the instructions needed to fix this issue.
GeneralUser-NonDev commentedon Jun 20, 2023
FINALLY got the update to 26.x.x to work, being new to all this stuff i had to first figure out WHERE to try running these commands. I had to open the containers console (terminal) and run the command "updater.phar" there, no clue where to use "docker exec -it nextcloud updater.phar" as it didn't work in the containers terminal/console window (maybe Unraid terminal window?!). after it finally taking 26 i removed the version tag on the repo line and it works correctly, currently trying to update to 27.x.x (and beyond) the same way, hope it works (knock on wood).
too bad there isn't a way to have the internals of the container to auto-update, or is there and I'm missing something?
nemchik commentedon Jun 20, 2023
It's being worked on #317
jkrauss82 commentedon Aug 15, 2023
Don't know why this issue is closed, it should not be.Just ran into the issue, too. We are on stable channel, nextcloud version 25.0.10, non-docker installation. We do not want to switch to a beta channel for production software.Documentation says recommended php is 8.2. We use apache2 and php-fpm.Request reopening and fixing this problem or update the documentation to be informative about actually supported environment.j0nnymoe commentedon Aug 15, 2023
You're on a non-docker installation. This support thread isn't relevant for you.
jkrauss82 commentedon Aug 15, 2023
Understood, nevermind.