Nextcloud version : 13
Operating system and version : Ubuntu server 16.04.3 LTS
Apache or nginx version : Apache 2.4.18
PHP version : 7.0.25
The issue you are facing:
Security & setup warnings It's important for the security and performance of your instance that everything is configured correctly. To help you with that we are doing some automatic checks. Please see the Tips & Tricks section and the documentation for more information. 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…) Please double check the installation guides ↗, and check for any errors or warnings in the log.
When investigating the cause I see this:
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 ======= - core - EXTRA_FILE - .well-known/acme-challenge/.htaccess Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [.well-known/acme-challenge/.htaccess] => Array ( [expected] => [current] => lkjfdgpo8745pwtoisgjfoidup9yt8w45u09u86ysjro9hu5rt9jihjhsaevlfiugzkuygVra7w83385o1409q86aghho938iu4blgv8gh4oiu3hto98yaeg98yae4a9p84e9t5 ) ) ) )
Is this the first time you’ve seen this error? : N
Steps to replicate it:
- go to … .com/index.php/settings/admin#security-warning page.
The output of your Nextcloud log in Admin > Logging:
Error no app in context issuetemplate 2018-02-28T13:53:47-0500
The output of your config.php file in
/path/to/nextcloud/config (make sure you remove any identifiable information!):
<?php $CONFIG = array ( 'instanceid' => '', 'passwordsalt' => '', 'secret' => '', 'trusted_domains' => array ( 0 => '.com', ), 'datadirectory' => '', 'overwrite.cli.url' => 'https://com', 'dbtype' => 'mysql', 'version' => '126.96.36.199', 'dbname' => '', 'dbhost' => '', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => '', 'dbpassword' => '', 'installed' => true, 'mail_from_address' => '', 'mail_smtpmode' => 'smtp', 'mail_smtpauthtype' => '', 'mail_domain' => '', 'mail_smtphost' => 'smtp.mailgun.org', 'mail_smtpport' => '587', 'mail_smtpauth' => 1, 'mail_smtpname' => '', 'mail_smtppassword' => '', 'maintenance' => false, 'memcache.local' => '\OC\Memcache\APCu', );
I think this as ignorable error, but it can’t be ignored cause it’s always popping up to annoy me. I believe that the way my Let’s Encrypt certificates are managed is what caused this error. I’m wondering if their’s some way to get the scan to ignore that
.well-known/acme-challenge/.htaccess folder and/or file.
It’s not obvoious, but I did my install in a subdomain in such a way that the nextcloud folder is not part of the URL for the system. Thus the let’s encrypt sees the root as the nextcloud subfolder and boom, I got a problem.