Open_basedir restriction after update to 26

@camouflage81 We just moved to another hosting that is using Plesk. A simple workaround on Plesk is by going to Websites & Hosting > PHP Settings and add {:}/proc/ to the open_basedir field. In our case the default was {WEBSPACEROOT}{/}{:}{TMP}{/} and I changed that to {WEBSPACEROOT}{/}{:}{TMP}{/}{:}/proc/

As I understand it there are 2 competing PR’s being discussed now on Github:

Check for open_basedir before reading /proc by solracsf · Pull Request #37959 · nextcloud/server · GitHub (already mentioned above)

and

In my experience, for small scale Nextcloud setups on shared hosting the only issue is the flood of open_basedir restriction errors in the log. We encourage our (35) users to only use the clients and we’re not seeing any performance issues.