Warning - shell_exec() has been disabled for security reasons - Matomo 4.4.0

Hello,

I’ve gotten the following alert since updating to 4.4.0. The same message occurs with both Process.php(317), Process.php(283), and Process.php(215). It does not appear to have already been posted here. I believe shel_exec is disabled by my hosting service for security reasons. Is there something else I need to do or fix?

Thanks!

WARNING: /home/xxxx/public_html/matomo/core/CliMulti/Process.php(283): Warning - shell_exec() has been disabled for security reasons - Matomo 4.4.0 - Please report this message in the Matomo forums: https://forum.matomo.org (please do a search first as it might have been reported already) (Module: Installation, Action: systemCheckPage, In CLI mode: false)

Hi. After updating to 4.4.0 I have the same issues like you
" WARNING: /home/xx/domains/xx.com/public_html/analytics/core/CliMulti/Process.php(283): Warning - shell_exec() has been disabled for security reasons - Matomo 4.3.1 - Please report this message in the Matomo forums: (please do a search first as it might have been reported already) (Module: CoreUpdater, Action: oneClickUpdate, In CLI mode: false)

WARNING: /home/xx/domains/xx.com/public_html/analytics/core/CliMulti/Process.php(317): Warning - shell_exec() has been disabled for security reasons - Matomo 4.3.1 - Please report this message in the Matomo forums: (please do a search first as it might have been reported already) (Module: CoreUpdater, Action: oneClickUpdate, In CLI mode: false)

WARNING: /home/xx/domains/xx.com/public_html/analytics/core/CliMulti/Process.php(251): Warning - shell_exec() has been disabled for security reasons - Matomo 4.3.1 - Please report this message in the Matomo forums: (please do a search first as it might have been reported already) (Module: CoreUpdater, Action: oneClickUpdate, In CLI mode: false)"

1 Like

Hi,

Can you see if this change fixes it for you:

It should also be included in the 4.4.1 release candidate

1 Like

OK - thanks! I’ll be sure to update when the update is available.

Thank you - that did indeed fix the issue.