Unexpected FPM behaviour for domain users: You are not allowed to manage this PHP configuration file

[fakemoth]

This happens on a few Debian and Ubuntu machines, both in Virtualmin GPL and Pro. When logged in as the user of a domain, the Services > PHP-FPM Configuration menu entry throws "You are not allowed to manage this PHP configuration file".

I activated all and other related options mostly in System Settings > Server Templates > your template > PHP options and in System Settings > Server Templates > your template > Administrator's Webmin modules.

As root it works, but not as a domain user, so looked at the permissions of /etc/php/7.4/fpm/pool.d/0123456789.conf (stated on the page as root) and those are: root:root | 0644. So the user can't write in this case. Is there some option that I missed, or what is the expected behavior, also security conscious?

[willnode]

The UI maybe little confusing for domain user but I imagine if users actually allowed to change FPM port there, that would ruin the whole server if there's mismatch in Apache config or a duplicate port in FPM mode.

[jcameron]

That "You are not allowed to manage this PHP configuration file" error can happen if you recently added a new PHP version to the system. To fix it, login as root, edit the virtual server, and click Save.

Note that even when the domain owner has access, they still can't change the FPM port - only PHP variables.

[marclaporte]

This is fixed by:
4c6068a

We can close this.

[iliajie]

There are more issues for domain owner described here - virtualmin/virtualmin-nginx#24 (comment)