MultiPHP vs Select PHP Version
Two tools that both set the PHP version. Which one to use, and what happens when you use both.
cPanel offers Select PHP Version and MultiPHP Manager, and both set a PHP version. Applies to shared and reseller hosting.
Use Select PHP Version. Reach for MultiPHP only when you need different versions on different domains within one account.
The difference
| Select PHP Version | MultiPHP Manager | |
|---|---|---|
| Scope | The whole account | Per domain |
| PHP builds | alt-php — security-patched | Stock cPanel builds |
| Versions offered | More, including patched older ones | Fewer |
| Extensions | Enable and disable per account | Not available |
| Settings | memory_limit and others, in the interface | Not available |
Why Select PHP Version is the default answer
It uses alt-php, CloudLinux's hardened builds. These carry security patches
backported to versions upstream no longer supports — so an older version remains
patched against known vulnerabilities, where the stock build of the same version
does not.
It manages extensions and settings. Enabling redis, or raising
memory_limit, is done here. MultiPHP cannot do either — see
Change your PHP version and settings.
When MultiPHP is the right tool
Only for genuinely different versions across domains in one account — an old
application on legacy.example.com needing PHP 7.4 while the main site runs 8.3.
Setting a version in MultiPHP for a domain overrides the account-level
version from Select PHP Version for that domain — including its extensions and
settings. A domain switched in MultiPHP loses the redis extension you enabled
in the Selector, with no indication that it has.
This is the usual explanation for "I enabled the extension and the site still cannot see it".
Which is actually in effect
<?php echo PHP_VERSION;Delete the file afterwards. If it disagrees with Select PHP Version, check MultiPHP Manager for a per-domain override.
Neither applies on Bolt-Cache, which runs NGINX with PHP-FPM. There the
version is set when Bolt-Cache is configured, and settings come from
.user.ini — see
Change your PHP version and settings.
Related
Run PHP inside .html files
Make the server execute PHP in files with a .html or .htm extension, using the correct handler for WebGee's LiteSpeed setup.
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.