# Disable code integrity check

**URL:** <https://help.nextcloud.com/t/disable-code-integrity-check/31289>\
**Category:** ℹ️ Support\
**Tags:** integrity-check, nc13\
**Created:** [May 4, 2018, 1:51pm UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289 "2018-05-04T13:51:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ygoe](https://help.nextcloud.com/letter_avatar/ygoe/32/5_5575768a8748004e209b776fc1b2916d.png) [@ygoe](https://help.nextcloud.com/u/ygoe)\
**Post date:** [May 4, 2018, 1:51pm UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289/1 "2018-05-04T13:51:01Z")

</div>

After recovering from a miserably failed automatic upgrade by restoring a backup, and then trying a manual upgrade, I had to fix the .htaccess file again to make it work correctly. Apache says “Options are not allowed here” so I commented out the two lines that used Options.

Now Nextcloud always shows the message “Bei der Code-Integritätsprüfung sind Probleme aufgetreten.” at the top of each page. A listing shows that the .htaccess file was modified and two extra files in cgi-bin were found. That is correct and totally required to make Nextcloud work at all.

Can I get rid of this check? Alternatively, can I teach it that what it found was not unexpected but correct and necessary?

This is Nextcloud 13.0.2 on Ubuntu 16.04.

---

<div class="post-metadata">

**Author:** ![anon99252149](https://help.nextcloud.com/letter_avatar/anon99252149/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon99252149](https://help.nextcloud.com/u/anon99252149)\
**Post date:** [May 4, 2018, 1:59pm UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289/2 "2018-05-04T13:59:19Z")

</div>

> [@ygoe](#):
>
> Can I get rid of this check?

Yes: Modify `/config/config.php` and set

```auto
'integrity.check.disabled' => true,

```

That’s all.

---

<div class="post-metadata">

**Author:** ![zlg](https://help.nextcloud.com/user_avatar/help.nextcloud.com/zlg/32/12222_2.png) [@zlg](https://help.nextcloud.com/u/zlg)\
**Post date:** [July 27, 2019, 8:48pm UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289/3 "2019-07-27T20:48:14Z")

</div>

Setting that did not work for me on NC14 or NC15. Is it possible that NC forces integrity checks now?

---

<div class="post-metadata">

**Author:** ![Tas-sos](https://help.nextcloud.com/user_avatar/help.nextcloud.com/tas-sos/32/4251_2.png) [@Tas-sos](https://help.nextcloud.com/u/Tas-sos)\
**Post date:** [August 8, 2019, 6:46am UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289/4 "2019-08-08T06:46:13Z")

</div>

With all my respect, maybe this is a bad approach?  
Why to disable code integrity check ?

In this topic mention a different solution

> [@Integrity check failed core -\> extra file -\> .rnd](https://help.nextcloud.com/t/integrity-check-failed-core-extra-file-rnd/41958):
>
> Typically would follow the standard support template but this issue seems generic and not OS dependent. Fresh install of 14.0.4 on Ubuntu 18.10. Getting an integrity check fail but I can’t seem to pinpoint what’s causing it. Initially had it fail because of the tar archive left in the web-root but upon removing that, its complaining about a .rnd file. I had a suspicion this was related to the first fail so I wiped the directory and started fresh. Everything else works fine but it’s bugging me t…

Thank you.

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 4, 2024, 7:01am UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289/5 "2024-12-04T07:01:31Z")

</div>



---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 9, 2024, 2:41pm UTC](https://help.nextcloud.com/t/disable-code-integrity-check/31289/6 "2024-12-09T14:41:53Z")

</div>


