Closed stanthewizzard closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
With the exception of the files listed under core
each of the sections named should be a folder inside /config/www/nextcloud/apps/
and the files listed under that section should exist within. You will need to manually remove those files.
To remove the files under the core section, you will need to recreate the container (not just restart). If you're using docker compose, you can run docker compose down
and then docker compose up
This issue seems to be happening to everyone, but the files listed depend on the apps installed in each individual nextcloud instance, so I haven't found a way to automate cleanup yet.
I'm also having the same issue, running in a docker on unraid. Should I expect a future fix patch or am I required to take action to solve the issue?
same here, just updated on unraid and now im seeing this :(
https://github.com/linuxserver/docker-nextcloud/pull/325 should fix the integrity check issue
A test image is available here:
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-06ca2ef0a15179a65b6a1d869563b3729cf93cbb-pr-325
Before running the image, run the following command to force the init logic to reinstall the files (which should fix the integrity check):
docker exec nextcloud touch /config/www/nextcloud/config/needs_migration
I've tested this on my personal instance, and a few other team members plan to test as well, but additional confirmations would be great. We'll merge these changes and release a stable build as soon as we have enough confirmations.
That’s what I did. Removed photo. Reup. Worked. And did that for all the apps
325 should fix the integrity check issue A test image is available here:
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-06ca2ef0a15179a65b6a1d869563b3729cf93cbb-pr-325
Before running the image, run the following command to force the init logic to reinstall the files (which should fix the integrity check):docker exec nextcloud touch /config/www/nextcloud/config/needs_migration
I've tested this on my personal instance, and a few other team members plan to test as well, but additional confirmations would be great. We'll merge these changes and release a stable build as soon as we have enough confirmations.
does this work on unraid?
can i safely use nextcloud even if i don't fix this error?
I had this issue yesterday and reverted to a backup. I was wondering if my issue was not to upgrade from a docker image defining nextcloud 26 to one on nextcloud 27 without upgrading first nextcloud. Should both be kept to the same version. I am currently stuck, Maps application cannot be upgraded to a version greater than 26.0.2 and OpenID connect is not yet mark as functionnal for 27.
I reverted the installation to the 26.0.2-ls248 image, and a 20.0.2 installation on my mount. I guess this is the safest bet here.
does this work on unraid?
yes
can i safely use nextcloud even if i don't fix this error?
yes
I had this issue yesterday and reverted to a backup. I was wondering if my issue was not to upgrade from a docker image defining nextcloud 26 to one on nextcloud 27 without upgrading first nextcloud. Should both be kept to the same version. I am currently stuck, Maps application cannot be upgraded to a version greater than 26.0.2 and OpenID connect is not yet mark as functionnal for 27.
I reverted the installation to the 26.0.2-ls248 image, and a 20.0.2 installation on my mount. I guess this is the safest bet here.
If you have apps that require specific compatibility, your best bet is to pin your docker image to a specific version that is compatible with all your apps, and if that version is below 27 you should manually update the install files to that version of nextcloud. If you delete /config/www/nextcloud/index.php
while using an image tagged for 26 or below and then restart the container it should reinstall the core files to the tagged version. You would then also want to run occ upgrade
inside the container to be sure everything is up to date for the version you're on.
325 should fix the integrity check issue A test image is available here:
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-06ca2ef0a15179a65b6a1d869563b3729cf93cbb-pr-325
Before running the image, run the following command to force the init logic to reinstall the files (which should fix the integrity check):docker exec nextcloud touch /config/www/nextcloud/config/needs_migration
I've tested this on my personal instance, and a few other team members plan to test as well, but additional confirmations would be great. We'll merge these changes and release a stable build as soon as we have enough confirmations.
Didn't work for me unfortunately. This is what I did:
touch /config/www/nextcloud/config/needs_migration
inside the Docker containerlscr.io/linuxserver/nextcloud:27.0.0
to lspipepr/nextcloud:27.0.0-pkg-34240624-dev-06ca2ef0a15179a65b6a1d869563b3729cf93cbb-pr-325
I also did it twice (second time just restarting the container instead of changing the image tag), as I wasn't sure if I forgot creating the needs_migration
file at the first try. But also after the second try, the integrity check still fails.
This is the output (seems to only be about not-preinstalled apps):
@koelle25 can you try re-running touch /config/www/nextcloud/config/needs_migration
and then switching the image to lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
(new) and then if you have issues, post your container log, nextcloud log (from /data), and any error messages from the web admin status page here?
@koelle25 can you try re-running
touch /config/www/nextcloud/config/needs_migration
and then switching the image tolspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
(new) and then if you have issues, post your container log, nextcloud log (from /data), and any error messages from the web admin status page here?
It's work, thanks.
my env: TrueNAS-SCALE-22.12.3.1 not installed in TN's app store
my flow:
docker exec -it k8s_ix-chart_nextcloud-ix-chart-fc56cd8fc-l2x69_ix-nextcloud_zxy /bin/bash
touch /config/www/nextcloud/config/needs_migration
chown abc:abc /config/www/nextcloud/config/needs_migration
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
Rescan
twice(I have no idea)Next question: Can i switch image back to ghcr.io/linuxserver/nextcloud:latest
, now?
Next question: Can i switch image back to
ghcr.io/linuxserver/nextcloud:latest
, now?
Yes
I have the same problem.
Did the
touch /config/www/nextcloud/config/needs_migration
change the img to
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
Recreated the pod inside Kubernetes, but still the same error.
Then I did hit Rescan and the error it's fixed.
This is part of the logs after the change:
using keys found in /config/keys Initializing nextcloud 27.0.0.8 (this can take a while) ... Upgrading nextcloud from 27.0.0.8 ... Setting permissions Nextcloud is already latest version Initializing finished
Did the same, switched back to
325 should fix the integrity check issue A test image is available here:
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-06ca2ef0a15179a65b6a1d869563b3729cf93cbb-pr-325
Before running the image, run the following command to force the init logic to reinstall the files (which should fix the integrity check):docker exec nextcloud touch /config/www/nextcloud/config/needs_migration
I've tested this on my personal instance, and a few other team members plan to test as well, but additional confirmations would be great. We'll merge these changes and release a stable build as soon as we have enough confirmations.
Tested and now everything appears to work fine, so I switched back the image to lscr.io/linuxserver/nextcloud:latest
I'm running the container on my server using Unraid and after performing the fix listed in the above the error went away, but now I can no longer run the OCC command.
Running:
docker exec -it nextcloud sudo -u abc php /config/www/nextcloud/occ
Results in:
Could not open input file: /config/www/nextcloud/occ
OK had and issue in unraid docker. I guess the upgrade is not as automatic as letting the container upgrade. I went back to the 26 major version (lscr.io/linuxserver/nextcloud:version-26.0.2). Dont mess with the web interface upgrade always getting errors. Open a console and run "occ upgrade". Then goto next version and run again.
I'm running the container on my server using Unraid and after performing the fix listed in the above the error went away, but now I can no longer run the OCC command.
Running:
docker exec -it nextcloud sudo -u abc php /config/www/nextcloud/occ
Results in:
Could not open input file: /config/www/nextcloud/occ
docker exec -it nextcloud occ
should work. You don't need the extra bits.
OK had and issue in unraid docker. I guess the upgrade is not as automatic as letting the container upgrade. I went back to the 26 major version (lscr.io/linuxserver/nextcloud:version-26.0.2). Dont mess with the web interface upgrade always getting errors. Open a console and run "occ upgrade". Then goto next version and run again.
The process you did is correct to get current. Once you're running Nextcloud 27 you can use the latest image and all future updates should be automatic when you update the container image.
This should be resolved now with the new image release.
@koelle25 can you try re-running
touch /config/www/nextcloud/config/needs_migration
and then switching the image tolspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
(new) and then if you have issues, post your container log, nextcloud log (from /data), and any error messages from the web admin status page here?
Thanks. It work for unraid Docker...
@koelle25 can you try re-running
touch /config/www/nextcloud/config/needs_migration
and then switching the image tolspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
(new) and then if you have issues, post your container log, nextcloud log (from /data), and any error messages from the web admin status page here?Thanks. It work for unraid Docker...
it say "No such file or directory"
it say "No such file or directory"
Step by Step
touch /config/www/nextcloud/config/needs_migration
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
linuxserver/nextcloud:latest
if the docker disappears for some reason, you specified the repository incorrectly. The Docker can then disappear. But don't worry, just go to ADD Container at the bottom of the docker and select Nextcloud and adjust the repository again.
Good luck!
The changes to fix the integrity check have been merged. The best option now is to run the latest image
lscr.io/linuxserver/nextcloud:latest
and run in the server terminal (not the container terminal)
docker exec -it nextcloud touch /config/www/nextcloud/config/needs_migration
docker restart nextcloud
That should make the init script cleanup the files, and then you can trigger a rescan in the nextcloud admin status page by clicking rescan.
it say "No such file or directory"
Step by Step
- Open Docker Console from Nextcloud
- execute the command
touch /config/www/nextcloud/config/needs_migration
- Close the Console
- Edit the Docker
- copy the original Repository link and save it
- Replace the Repository to
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
- Push applay
- Go to nextcloud and did hit Rescan and the error it's fixed.
- Back to the Docker Editor and change the Repository Link back to the original where you copy in point five. in my case it is
linuxserver/nextcloud:latest
- Push applay
if the docker disappears for some reason, you specified the repository incorrectly. The Docker can then disappear. But don't worry, just go to ADD Container at the bottom of the docker and select Nextcloud and adjust the repository again.
Good luck!
Worked! Thank you!
it say "No such file or directory"
Step by Step
- Open Docker Console from Nextcloud
- execute the command
touch /config/www/nextcloud/config/needs_migration
- Close the Console
- Edit the Docker
- copy the original Repository link and save it
- Replace the Repository to
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
- Push applay
- Go to nextcloud and did hit Rescan and the error it's fixed.
- Back to the Docker Editor and change the Repository Link back to the original where you copy in point five. in my case it is
linuxserver/nextcloud:latest
- Push applay
if the docker disappears for some reason, you specified the repository incorrectly. The Docker can then disappear. But don't worry, just go to ADD Container at the bottom of the docker and select Nextcloud and adjust the repository again.
Good luck!
Thanks @swiss01 , now it worked for me too. I also already changed back to the release tag (lscr.io/linuxserver/nextcloud:27.0.0
).
@nemchik
WORKS flawlessly thanks
it say "No such file or directory"
Step by Step
- Open Docker Console from Nextcloud
- execute the command
touch /config/www/nextcloud/config/needs_migration
- Close the Console
- Edit the Docker
- copy the original Repository link and save it
- Replace the Repository to
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
- Push applay
- Go to nextcloud and did hit Rescan and the error it's fixed.
- Back to the Docker Editor and change the Repository Link back to the original where you copy in point five. in my case it is
linuxserver/nextcloud:latest
- Push applay
if the docker disappears for some reason, you specified the repository incorrectly. The Docker can then disappear. But don't worry, just go to ADD Container at the bottom of the docker and select Nextcloud and adjust the repository again.
Good luck!
EDIT: Nevermind. It works.
it say "No such file or directory"
Step by Step
- Open Docker Console from Nextcloud
- execute the command
touch /config/www/nextcloud/config/needs_migration
- Close the Console
- Edit the Docker
- copy the original Repository link and save it
- Replace the Repository to
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
- Push applay
- Go to nextcloud and did hit Rescan and the error it's fixed.
- Back to the Docker Editor and change the Repository Link back to the original where you copy in point five. in my case it is
linuxserver/nextcloud:latest
- Push applay
if the docker disappears for some reason, you specified the repository incorrectly. The Docker can then disappear. But don't worry, just go to ADD Container at the bottom of the docker and select Nextcloud and adjust the repository again. Good luck!
EDIT: Nevermind. It works.
Same here, in the end it worked, dont be irritated if the failure is still present after the first edit, in my case it was gone after going back to the latest one.
Hi All!
Got here the same error and was hoping i could you this fix to.. but i'm running a newer version atm.. 27.0.1.2
Can't start Nextcloud because the version of the data (27.0.1.2) is higher than the docker image version (27.0.0.8) and downgrading is not supported. Are you sure you have pulled the newest image version?
Is there any way to fix this ?
Hi All!
Got here the same error and was hoping i could you this fix to.. but i'm running a newer version atm.. 27.0.1.2
Can't start Nextcloud because the version of the data (27.0.1.2) is higher than the docker image version (27.0.0.8) and downgrading is not supported. Are you sure you have pulled the newest image version?
Is there any way to fix this ?
Update: Cheated the system a little...
Edited the config.php file to bypass this error, bring up the new container and is worked! did a semi manuel update by browser, switches back to the common version and all was back on track! Love it! Thanks!
From this point, don't update nextcloud via the web. Just update the container image when we release new versions (usually within an hour or so after nextcloud releases a new version).
From this point, don't update nextcloud via the web. Just update the container image when we release new versions (usually within an hour or so after nextcloud releases a new version).
Thanks for the reply! What would be the right way to update? Got nextcloud running by docker-compose but every time i do a "docker-compose up -d" i get an error bla bla permission denied... had to kill it en restart the complete environment
From this point, don't update nextcloud via the web. Just update the container image when we release new versions (usually within an hour or so after nextcloud releases a new version).
Thanks for the reply! What would be the right way to update? Got nextcloud running by docker-compose but every time i do a "docker-compose up -d" i get an error bla bla permission denied... had to kill it en restart the complete environment
That sounds like an issue how you have set up your compose or file permissions. Updating via docker compose up
should be all you need to update nextcloud.
From this point, don't update nextcloud via the web. Just update the container image when we release new versions (usually within an hour or so after nextcloud releases a new version).
Thanks for the reply! What would be the right way to update? Got nextcloud running by docker-compose but every time i do a "docker-compose up -d" i get an error bla bla permission denied... had to kill it en restart the complete environment
That sounds like an issue how you have set up your compose or file permissions. Updating via
docker compose up
should be all you need to update nextcloud.
Thanks! The "-d" is causing the permission denied error from docker ?
no, the -d
means daemon
which runs the containers in the background and returns you to a prompt. Without it, you have to keep the terminal running or the containers stop (they won't run in the background).
no, the
-d
meansdaemon
which runs the containers in the background and returns you to a prompt. Without it, you have to keep the terminal running or the containers stop (they won't run in the background).
What could be the cause of the error? Pid user rights?
Could you post the full log here from when you run the command?
Could you post the full log here from when you run the command?
Something simple as: sudo docker stop nextcloud Error response from daemon: cannot stop container: nextcloud: permission denied
compose config:
version: "2.1" services: nextcloud: image: lscr.io/linuxserver/nextcloud:latest container_name: nextcloud environment:
Could it be the PUID PGID ?
Root hass 0 and Common user has the 1000 ?
That seems like your user isn't in the docker group. You could add your user to the docker group or run the command with sudo.
Is there an existing issue for this?
Current Behavior
After update I have inside administration settings
Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the [documentation ↗]
The files incriminated:
`Technical information
The following list covers which files have failed the integrity check. Please read the previous linked documentation to learn more about the errors and how to fix them.
Results
Raw output
Array ( [core] => Array ( [EXTRA_FILE] => Array ( [dist/files_trashbin-files_trashbin.js] => Array ( [expected] => [current] => 24e537aff151f18ae18af31152bcfd7de9c96f0f6fdcca4c1ad975ece80bb35a2ab7d51c257af6a9762728d7688c9ba37a5359a950eb1e9f401d4b9d875d92b2 )
)`
Expected Behavior
Green flag
Steps To Reproduce
Update to the new container nextcloud 27
Environment
CPU architecture
x86-64
Docker creation
Container logs