-
-
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
There were problems with the code integrity check. More information... #12051
Comments
Can you try to regenerate the .htaccess file with |
GitMate.io thinks possibly related issues are #1502 (There were some problems with the code integrity check), #9375 (Code integrity check), #1398 (Problems with code integrity when skeleton folder is empty), and #9696 (The Phone Track app hangs it's progress icon indefinitely). |
@nextcloud-bot None of these topics were good guesses for the problem. |
@violoncelloCH I tried and here are the results:
I tried it after changing ownership to |
The normal way would be to leave ownership to user www-data (and group www-data) and use |
Try to append a |
@violoncelloCH I believe my settings were from the Nextcloud sites security recomendations. I tried numerous combinations of
@danielkesselberg I added it to the end, so it was
It's not the wrong URL, but perhaps my Apache settings are non-standard? Here's details on mine from having this problem with NC13. https://help.nextcloud.com/t/some-files-have-not-passed-the-integrity-check-double-htaccess-file-due-to-lets-encrypt/28270/5?u=ruppscloudadmin Can't I just do something to get the right hash it's complaining about in the right place?
|
Could you share |
|
Who is the owner/group of your .htaccess? |
@danielkesselberg I've tried it a number of ways. For background, I manage my server with Virtualmin, and my Nextcloud runs in a subserver of a virtual server (subdomain, domain). The subserver and virtual server have the same user as their admin user, but that user is not an admin of the main real server. |
Re @danielkesselberg
A second go at this tonight with the appended /
After the appended / your update command ran but did not solve the problem. Closing this one because I started a new one... |
Steps to reproduce
Expected behaviour
The .htaccess files don't go shit haywire.
Actual behaviour
Something goes wrong most often on an upgrade. I struggle to get the error banner to clear. I get it right and forget how I did it last time. I upgrade and it's f-ked again.
Server configuration detail
Operating system: Linux 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 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: 13
Where did you install Nextcloud from: The Nextcloud site originally
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: no
Are you using encryption:
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
Operating system: Ubuntu 18.04.1 LTS
Logs
Browser log
Nextcloud log
Browser log
The text was updated successfully, but these errors were encountered: