There's a forum thread with a handful of issues with PHP-FPM support and validation of virtual servers using PHP-FPM:
https://www.virtualmin.com/node/51833
Some of these seem like they ought to be automatic, maybe during the postinstall wizard, or during the install script. (If we were to commit to PHP-FPM as the only execution type for PHP scripts, we could make it part of the install script, but it might be a little early for that...we need a lot more testing in the wild).
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Sat, 04/15/2017 - 00:42 Comment #1
So it sounds like the suggestion from that thread is that PHP-FPM support not be offered if the needed perl modules are missing?
Submitted by 7stars on Sat, 04/15/2017 - 09:28 Comment #2
why perl modules? Apache modules... mod_proxy... are Apache modules
eg. here on CentOS 7
/etc/httpd/conf.modules.d/00-proxy.conf
fpm just needs:
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
other proxy modules better not...
so, if they aren't loaded, you should report that in the Re-Check Configuration... eg. in this case "
PHP-FPM is installed and running BUT mod_proxy_... is/are not loaded
" so you can't add ProxyPassMatch on the vhost rules...and then, don't allow users to switch to php-fpm on
Server Configuration → Website Options
OR when users save for php-fpm make sure those modules are loaded and, if not, uncomment/add the
LoadModule...
directives and restart ApacheSubmitted by 7stars on Sat, 04/15/2017 - 09:18 Comment #3
just a note: I don't know how it works with nginx... maybe at first you should check what webserver is currently in use
Submitted by JamieCameron on Sat, 04/15/2017 - 11:40 Comment #4
Sorry, I meant Apache module.
The next release of Virtualmin will add these checks.
Submitted by JamieCameron on Sat, 04/15/2017 - 11:40 Comment #5
Submitted by IssueBot on Sat, 04/29/2017 - 11:42 Comment #6
Automatically closed - issue fixed for 2 weeks with no activity.