-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Integrity check failed on Nextcloud 16.0.1 #15681
Comments
I added those files manually (actually the entire l10n folder was missing under /apps/accessibility/) and run a new integrity check but it failed anyway. |
I can confirm this issue on FreeBSD 11.2-STABLE (FreeNAS custom jail). Installing the files manually and setting permissions didn't help. |
i encountered the same issue following the same steps |
Same issue on FreeNas11.2-U4.1 (FreeBSD 11.2-STABLE). |
Any news on it? Seems like the scan is expecting something more thant what actually exists. |
As I cannot reproduce the original issue anymore, I will close this ticket. If this is still happening please make sure to upgrade to the latest version. After that, feel free to reopen. |
I do confirm, seems like it is OK with the latest release. |
Steps to reproduce
Expected behaviour
No integrity fails
Actual behaviour
Server configuration
Web server: FreeBSD 11.2-RELEASE-p9
Database: mysql 5.6.44
PHP version: 7.1.28
Nextcloud version: 16.0.1.1
Updated from an older Nextcloud/ownCloud or fresh install: updated from 16.0
Where did you install Nextcloud from: pkg
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser:
Operating system:
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: