-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Some files have not passed the integrity check. Upgrading v27 -> v28.0.0 #386
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I can confirm this error. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Possible Fix? In this topic I found the link to the official downloads of nextcloud. Then I downloaded version 28.0.0 and extracted it. Then I copied the file nextcloud-28.0.0/nextcloud/core/js/mimetypelist.js to my unraid server On my unraid server, I shut down the nextcloud container and went into the nextcloud folder: cd /mnt/user/appdata/nextcloud/nextcloud/core/js mv mimetypelist.js mimetypelist.js.bak Then I copied the mimetypelist.js file I copied earlier on the server into the /mnt/user/appdata/nextcloud/nextcloud/core/js folder and set the right ownership for the file (chown nobody:users mimetypelist.js and chmod -x mimetypelist.js). Then I started the nextcloud container and after a rescan in the administration settings the error was gone. I don't know, if this is the best solution, but at least the error is gone. |
Can confirm this is solved now by updating to version 28.0.1 |
Is there an existing issue for this?
Current Behavior
After upgrading to v28.0.0
In Nextcloud Administrator settings -> Security & setup warnings
-> Some files have not passed the integrity check.
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
(
[INVALID_HASH] => Array
(
[core/js/mimetypelist.js] => Array
(
[expected] => 550ab566d30693bfa24ec4b15d9df87731ae8a3be8f79dabf94757e5b8b20eec6e4b678f17af1718297f2872f6b04519eeb024d1dff11947f29da431c7f11201
[current] => 24e6faa4a1361e51ff70027024f41c4b37fdb5f6f347ceb095450ddbde2d0a6b6dd1403be92a912d2889064a9736a9bed89d7dc62470035fc1299d4b977c5f46
)
)
Expected Behavior
No error or all files passing the integrity check
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Branch Version Built latest 28.0.0 12 Dec 2023 at 13:04:11 portainer stack: version: "2.1" services: nextcloud: image: linuxserver/nextcloud:latest container_name: nextcloud environment: - TZ=Europe/Amsterdam volumes: - nc_config:/config - nc_data:/data networks: - nextcloud_default - local-net ports: - 444:443 restart: unless-stopped
Container logs
The text was updated successfully, but these errors were encountered: