Permanent fix for integrity file check error on nextcloud.log file (and for any file)

For years, we are hundreds having the same problem with nextcloud.

How to fix integrity file error ? Is there an exclusion list ?

For my exemple, in maintenance mode, the command integrity:check-core returns a message as follow:

Nextcloud is in maintenance mode, no apps are loaded.
Commands provided by apps are unavailable.

  • EXTRA_FILE:
    • nextcloud.log:
      • expected:
      • current: cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e

just deleting the file and rerun occ integrity:check-core does not do the job.

I see message about integrity file error on this forum since 2016. And honestly, I still don’t know how to fix it permanently with 100% success.

Please help and we can really close all topics related to this issue :slight_smile:

I love Nextcloud, I love using Nextcloud, I use it for 10 years or more :slight_smile:

I have a guess. Please post the output of:

occ config:system:get logfile

and:

occ config:system:get datadirectory

According to your post, your nextcloud.log is located in the web root of your Nextcloud. The log does not belong there, which is why the warning is correct. Since Nextcloud has a more reasonable standard, I suspect a misconfiguration of your nextcloud/setup.

PS: This could also be a security issue. If you’re unlucky, everyone can access the log at /nextcloud.log without authentication. It depends, of course, on how the rest is configured.

3 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.