Why PHP-FPM is not available
WebGee runs LiteSpeed with mod_lsapi rather than PHP-FPM. What that means for you, and why the substitution is not a downgrade.
PHP-FPM cannot be enabled on WebGee shared and reseller accounts. The servers run
LiteSpeed Enterprise with the mod_lsapi handler instead.
Why
PHP-FPM is designed for Apache and NGINX. LiteSpeed has its own handler,
mod_lsapi, which is built for it and performs better in that pairing —
lighter per-request overhead and better behaviour under concurrency.
Running PHP-FPM alongside LiteSpeed would mean giving up what makes LiteSpeed worth using, in exchange for a handler it is not designed around.
What you actually lose
In practice, nothing you would use on shared hosting:
| PHP-FPM feature | On WebGee |
|---|---|
| Process pool tuning | Managed by LiteSpeed |
pm.max_children and similar | Not applicable |
Per-pool php.ini values | Use Select PHP Version → Options |
| OPcache | Enabled |
| Version switching | Select PHP Version |
Everything most applications document as "requires PHP-FPM" is really "requires
a persistent PHP handler rather than CGI" — which mod_lsapi is.
If something insists on PHP-FPM
Some applications check for it by name rather than by capability. That check is usually cosmetic and the application runs correctly regardless — try it before concluding it will not work.
Where it genuinely will not, a VPS gives you full control of the stack, including PHP-FPM if you want it — see Set up your cloud server.
Premium hosting
Bolt-Cache on Premium plans does run NGINX with PHP-FPM. If you specifically
need that stack, it is available there — settings come from .user.ini rather
than the PHP Selector, see
Change your PHP version and settings.