-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation. (List of invalid files… / Rescan…) #12524
Comments
GitMate.io thinks possibly related issues are #3833 (files have failed the integrity check), #12051 (There were problems with the code integrity check. More information...), #115 (.user.ini not passed the integrity check), #7233 (Contacts List Issue Not Resolved Sensibly), and #1366 (Integrity Check: add files/change files). |
I'm not sure why you created a new issue but at least you closed the old one 👍 Could you post the content of |
Having the same issue... this is idiotic. Let me reign over my own .htaccess and .user.ini! They are not (really) part of Nextcloud, but of my damn webserver, which I configure as I wish. Please exclude those files from the integrity check. This is overkill. |
server/lib/private/IntegrityCheck/Checker.php Lines 213 to 227 in 72e745b
@Chrisly3ear @WNYmathGuy is this not working for you (everything you put below |
@danielkesselberg No, unfortunately this doesn't work for me, because I'm using Nginx with php-fpm. Therefore I have to use a ".user.ini" instead of a ".htaccess" file. This is straight from the documentation (https://docs.nextcloud.com/server/13/admin_manual/configuration_files/big_file_upload_configuration.html#configuring-your-web-server) So, if I change the php configuration using the ".user.ini" file I get the "signature check failed" error. This is rather annoying, so I had to turn the whole code sigining thing off via config.php. I'm all for keeping the base system tamper proof, but not at the price of no custom webserver configs. Chris |
You could try the patch above (but please backup lib/private/IntegrityCheck/Checker.php before). Then use the default
Edit: Made a mistake. You need to remove the statement below after applying the patch. server/lib/private/IntegrityCheck/Checker.php Lines 205 to 211 in 72e745b
|
@danielkesselberg the one in the
The one in the web root folder has:
and the one in
The nextcloud-bot caught me on the old post that I forgot about and the old post seemed less "on the nose" than it could have been so I closed the old one. I agree that the code integrity check should not be disabled. The lies we tell ourselves are eventually catastrophic. |
That looks amazing, but I don't understand it. 😞 |
When you first run |
@danielkesselberg at the shell prompt:
Yesterday I moved the |
Just as reference #663 I never noticed a .htaccess inside .well-known/acme-challange/. Does letsencrypt renew work when you remove it? |
The hash of .htaccess does not match because this line is not expected.
I know there is warning when Referrer-Policy is not set. For nextcloud 14.0.3 something like below should be added after
Starting with nextcloud 14.0.4 (not released, testing right now) Referrer-Policy is set by default (#11798). Obviously I was wrong about Line 492 in 14f7b2c
#### DO NOT CHANGE ANYTHING ABOVE THIS LINE #### is replaced when you call php occ maintenance:update:htaccess 🙈
|
It might be something that Virtualmin does when it manages SSL on virtual servers. It's something I see in all my SSL enabled domains. |
Okay, @danielkesselberg just got back to it. Edit .htaccessI moved the .htaccess
RescanI then went into the admin web interface List of invalid files...
wtf?I wish I understood the in's and out's of these hash passings. How can I upgrade Nextcloud with Nextcloud from Nextcloud and have bad files? Do you know a link to some knowledge of what is going on with the hash passing and checking? I don't like to be ignorant but in this case I don't see the door out of the cave. I really wish I would have thought of using the details, summary tags earlier. Cleaner dialogue. |
|
DING! DING! DING! DING! DING! DING!🥇 hashtag-FTW! |
The reason I'm really here...
Where does the new current hash go? Can't I just paste the expected into a file somewhere? Or go backwards and paste the [current] into the file I see the [expected] hash?
Steps to reproduce
Expected behaviour
The installer installs without mucking up things. Maybe it moves offensive files and folders out, and then back in after it's done?
Actual behaviour
Described in "Steps to reproduce" section above.
Server configuration detail
Operating system: Linux 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64
Webserver: Apache/2.4.18 (cgi-fcgi)
Database: mysql 10.0.36
PHP version:
7.0.32-0ubuntu0.16.04.1
Modules loaded: Core, date, libxml, openssl, pcre, zlib, filter, hash, pcntl, Reflection, SPL, session, standard, cgi-fcgi, mysqlnd, PDO, xml, apcu, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imagick, imap, intl, json, ldap, exif, mcrypt, mysqli, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, shmop, SimpleXML, soap, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xmlreader, xmlrpc, xmlwriter, xsl, zip, Zend OPcache
Nextcloud version: 14.0.3 - 14.0.3.0
Updated from an older Nextcloud/ownCloud or fresh install: Updated from 13 to 14
Where did you install Nextcloud from: Nextcloud
Signing status
Array
(
[core] => Array
(
[INVALID_HASH] => Array
(
[.htaccess] => Array
(
[expected] => 70183f641f39fc5f43065aeb15b86ac99e86b82310d5467e1c4d935df30acc6155c0905f84f59616885275c19ffacea59e354a87a5c97c94f50d50d4eff0370e
[current] => e05ca07248d85fbaa8d0b033257dec1e62a1308462eba2e21a57eb574e2c4e41af3872d372f5d835f659f943010c4bceb7f3c8113b11eb65ff730e8a30f76a93
)
)
List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one:
Are you using encryption: true
Are you using an external user-backend, if yes which one:
Client configuration
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0
Operating system: Ubuntu 18.04 Workstation
The text was updated successfully, but these errors were encountered: