27.1.1 - Howto Reset INVALID_HASH on .htaccess to eliminate issue in 'Admin Overview'

Thank you, yes, I am just starting with nextcloud and I have not found were or how to add that exception. A link is fine if you have one. Is it in the admin manual or in the github wiki somewhere? I was hoping there was an occ command for it. I’ve looked at maintenance:update:htaccess and the integrity:... commands, but that doesn’t seem to be it. Where would I find how to do this?

I’ve found the source of the signature, nextcloud/core/signature.json, but I can’t see that I’m supposed to manually edit the file (which would then trigger it’s signature invalid), what do I use to update the .htaccess hash in that file? If the answer is:

  • A text editor,
  • sed, or
  • jq

I’m good with that, I just don’t want to create further problems without finding a reference for the way NC wants this done. (note: changing core/signature.json to include the correct sha512sum prevents the occ integrity:check-core from running properly)

Solution from Prior Post

NONE was necessary. I appears this has cropped up a time or to and a solution was posted at Integrity Check failed ->> .htaccess file invalid where you essentially add 'integrity.check.disabled' => true, to your config/config.php file, go to the Admin Overview, let it warn about the .htaccess file, click Rescan, log out/log in and finally remove the line added to config.php (personally, though not checked, the Rescan with the added line should be sufficient, then remove the line)