Some files have not passed the integrity check. NC 17.0.1

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 12.0.2): Nextcloud 17.0.1
Operating system and version (eg, Ubuntu 17.04): Ubuntu Server 18.04.3
Apache or nginx version (eg, Apache 2.4.25): 2.4.29
PHP version (eg, 7.1): 7.2.24

The issue you are facing:

I have just upgraded to Nextcloud 17.0.1 using the web updater.

I am getting this error in my System Administration section -
Some files have not passed the integrity check.

Results

  • text
    • EXTRA_FILE
      • .gitattributes
      • .eslintrc.js
      • .tx/config
      • .github/pull_request_template.md
      • .github/ISSUE_TEMPLATE/Feature_request.md
      • .github/ISSUE_TEMPLATE/Bug_report.md
      • README.md
      • package-lock.json
      • package.json
      • .l10nignore
      • l10n/.gitkeep

Is this the first time you’ve seen this error? (Y/N): Yes

I’d appreciate any help on this one, thanks.

Delete the file.

https://help.nextcloud.com/search?context=topic&context_id=64338&q=integrity%20check&skip_context=true

Hi, thanks for your tips on this.

It turns out that my nextcloud was using the older ‘Text’ app. Even disabling the app didnt remove the file integrity errors.

I had to go to my /var/www/nextcloud/apps/ folder and completely delete all the files in the ‘text/’ folder.

After restarting my server and running the integrity checks again got rid of this error.