Hi,
I’ve installed Nextcloud using this manual:
docs.mailcow.email Icon Nextcloud - mailcow: dockerized Dokumentation

docs.mailcow.email Icon docs.mailcow.email
Nextcloud - mailcow: dockerized Dokumentation
None
docs.mailcow.email

Now, if I open Admin > System I get an error:

0. /web/nextcloud/lib/private/AppFramework/App.php line 172
   OC\AppFramework\Http\Dispatcher->dispatch(OCA\Settings\Con ... {}, "index")
1. /web/nextcloud/lib/private/Route/Router.php line 298
   OC\AppFramework\App::main("OCA\\Settings\\ ... r", "index", OC\AppFramework\ ... {}, ["serverinfo","s ... "])
2. /web/nextcloud/lib/base.php line 1030
   OC\Route\Router->match("/settings/admin/serverinfo")
3. /web/nextcloud/index.php line 36
   OC::handleRequest()

Following this posts, it seems that I need to enable shell_exec:
Nextcloud community Icon Internal server failure on calling serverinfo

Nextcloud community Icon Nextcloud community
Internal server failure on calling serverinfo
Nextcloud version: 23.0.0 Operating system and version: Ubuntu 20.04 Apache or nginx version: 2.4.41 PHP version : 8.0 The issue you are facing: When accessing index.php/settings/admin/serverinfo on my NextCloud-instance, the server answers with an internal server failure. Let me highlight,
Nextcloud community

But how can I do this?

I was reading something about a .user.ini and indeed I found one:
/opt/mailcow-dockerized/data/web/nextcloud/.user.ini
However, If I get it right (php.net Icon PHP: Description of core php.ini directives - Manual

php.net Icon php.net
PHP: Description of core php.ini directives - Manual
phpphp8.3To Top
) the disable-functions is already empty, so the shell_exec should already be enabled.

I’m really confused. Can someone help me?

Given the error pertains to NextCloud and not Mailcow, you’ll get better help on their forums vs. here.

The error you’re receiving makes no mention of shell_exec(), unless if you excluded some of the error information. So I suspect that post you mentioned is unrelated to your problem.

Hard part with the guide from Mailcow docs is it doesn’t provide any version matrix for interoperability, so always possible that how Mailcow is integrating NextCloud into its Docker Compose no longer works with the latest version of NextCloud. You could try posting an issue in GitHub for mailcow to see if the helper script needs any revisions.

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

Ok, thanks, you might be right. The stacktrace doesn’t point out the “real” error message.
I was using the “formatted” error, the “raw” error tells:

"Previous":{"Exception":"Error","Message":"Call to undefined function OCA\\ServerInfo\\OperatingSystems\\shell_exec()","Code":0,"Trace":[{"file":"/web/nextcloud/apps/serverinfo/lib/OperatingSystems/DefaultOs.php","line":186,"function":"executeCommand","class":"OCA\\ServerInfo\\OperatingSystems\\DefaultOs","type":"->","args":["df -TPk"]},{"file":"/web/nextcloud/apps/serverinfo/lib/Os.php","line":78,"function":"getDiskInfo"

I didn’t ask the Mailcow community to fix the Nextcloud error.
I was asking how I could enable the shell_exec function, as it seems for me that this is disabled.
And as the PHP seems to be hidden in some container somewhere, I can’t edit the php.ini file.

So please, I you have an idea how to override the php.ini file, feel free to answer.

docker-compose.yml will often have file or folder drive mappings for the containers. That’ll be how you find the file(s) to edit.

Can you copy/paste the nextcloud section from your docker-compose.yml file?

I’m guessing you need to disable safe mode for PHP given you said there’s no explicitly disabled functions.

Did you check data/web/nextcloud/config/ as well?

Still recommend posting the same question in NextCloud forum as well, can’t hurt 😀

No one is typing