# Open\_basedir restriction after update to 26

**URL:** <https://help.nextcloud.com/t/open-basedir-restriction-after-update-to-26/158850>\
**Category:** ℹ️ Support\
**Tags:** nc26\
**Created:** [March 28, 2023, 11:51am UTC](https://help.nextcloud.com/t/open-basedir-restriction-after-update-to-26/158850 "2023-03-28T11:51:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ernolf](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ernolf/32/77874_2.png) [@ernolf](https://help.nextcloud.com/u/ernolf)\
**Post date:** [March 31, 2023, 9:55am UTC](https://help.nextcloud.com/t/open-basedir-restriction-after-update-to-26/158850/6 "2023-03-31T09:55:50Z")

</div>

> [@rawtaz](#):
>
> Why not just add /proc/cpuinfo to it instead?

The _open\_basedir_ is not been maintained, it still includes php73 directories. Nextcloud is secure enough IMHO, to disable open\_basedir.  
But of course, one could ad it as well but if this issue here already leads to a cry for help and the value has obviously not been maintained, I would recommend resetting the value, which is also the default.

So Adding /proc/cpuinfo alone is not enough, one have to adapt all the outdated pathes as well, which requires knowledge.

---

_[View the full topic](https://help.nextcloud.com/t/open-basedir-restriction-after-update-to-26/158850)._
