MultiPHP Manager – Setting PHP Version Per Domain

On iWebVault cPanel servers without CloudLinux, the PHP version for each of your domains is controlled by MultiPHP Manager — a native cPanel tool that lists every domain on your account and lets you pick which PHP version powers it. This guide walks through what MultiPHP Manager does, how to change versions safely, what changes after a switch, and how it differs from the CloudLinux PHP Selector you may have seen on other servers.

Where to find MultiPHP Manager

cPanel → Software section → MultiPHP Manager. The page shows a table of every domain on your account, the system default PHP version, and a dropdown per domain to override.

MultiPHP Manager vs CloudLinux PHP Selector — which is which

If your cPanel shows MultiPHP Manager but not Select PHP Version, you’re on a non-CloudLinux server — the workflow in this guide applies. If you see Select PHP Version, you’re on a CloudLinux server; see the PHP version guide for that environment.

Changing the PHP version for a domain

1. Open MultiPHP Manager.
2. Find your domain in the list.
3. Check the box next to it.
4. Use the PHP Version dropdown at the top right.
5. Pick the version you want (ea-php82, ea-php83, etc.).
6. Click Apply.

Effective immediately — next request hits the new version. No restart needed.

Batch change

Tick multiple domains, pick a version, Apply. All selected domains switch together.

Reverting to system default

Pick “inherit” from the dropdown. Domain follows whatever the server default is (set by your admin / WHM).

Picking the right version

For new WordPress sites in 2026, ea-php83 is a safe default. ea-php82 is the compatibility-first pick. Don’t run anything below 8.1 unless you must — older versions have known security issues and no upstream patches.

What changes after switching versions

• PHP itself. Different parser, different runtime. Old code using removed functions will error.
• Extensions available. Each ea-phpXX has its own enabled extension set on the server. Most common extensions (mysqli, curl, gd, intl, mbstring, zip) are available across versions.
• php.ini settings. Per-version ini files at /opt/cpanel/ea-phpXX/root/etc/php.ini. Settings you adjust in MultiPHP INI Editor apply only to the version you select there.
• Handlers. Most setups use PHP-FPM or LSAPI under the hood; the handler is configured at server level and usually doesn’t change with version selection.

Sites that work on PHP 8.1 usually work on 8.2 with minimal issues. 8.2 to 8.3 is also usually smooth. 7.4 to 8.x is the big jump — many deprecated features removed, type system stricter.

Testing before switching production

Bad version switches break sites instantly. Test first:

1. Create a subdomain (e.g. staging.yourdomain.com) pointed to a copy of your site.
2. In MultiPHP Manager, switch the staging subdomain to the new PHP version.
3. Browse the staging site; check admin areas, key pages, payment flows.
4. If broken: deprecated functions, removed features, plugin incompatibility. Fix or replace.
5. If clean: switch production with confidence.

For WordPress, enable WP_DEBUG_LOG on staging during the test (debug guide) — catches errors that don’t show on rendered pages.

Verifying which version is actually running

The MultiPHP Manager UI says what version should be in use. To verify what’s actually serving requests:

Method 1: phpinfo file

Create a file info.php in your site root:

<?php phpinfo(); ?>

Visit it in browser. The page shows PHP version at the top. Delete the file immediately after checking — it leaks server info.

Method 2: HTTP header

Browser DevTools → Network tab → response headers on any page. Look for X-Powered-By: PHP/8.X.X. (May not be present if the server hides this header — common on hardened setups.)

Method 3: WordPress dashboard

WP Admin → Tools → Site Health → Info tab → Server section. Shows PHP version.

Common MultiPHP Manager issues

“I switched versions but the site still shows old version.” Cache. LiteSpeed Cache, browser cache, or opcache. Purge LSCache and check again. For opcache specifically, ask support to restart PHP-FPM/LSAPI for the new version.

The system default vs. domain override

• The server has a system-wide default PHP version (set in WHM by admin).
• Each domain inherits that default unless you override in MultiPHP Manager.
• Once overridden, the domain stays at your chosen version even when the system default changes.
• Picking “inherit” returns the domain to using the system default.

If you have multiple domains and want them all on the same version, you can rely on the system default — but explicit per-domain settings are clearer when you read the panel later.

Common MultiPHP issues

“Domain not listed in MultiPHP Manager.” The domain may not be fully configured. Check Domains list in cPanel — if it’s there but missing from MultiPHP Manager, contact support.

“Switched to PHP 8.x and site broke with white screen.” Plugin or theme incompatible with newer PHP. Switch back via MultiPHP Manager (instant rollback), enable WP_DEBUG_LOG to identify the culprit, then upgrade or replace it.

“Extension I need isn’t available in the version I picked.” Check other versions — extensions vary across ea-phpXX builds. If genuinely missing across all versions, open a ticket.

“My .htaccess has PHP version directives — do those still work?” Maybe. Some AddHandler directives interfere with MultiPHP Manager. Remove old PHP-version directives from .htaccess and let MultiPHP Manager handle it.

“Changes don’t stick — domain reverts to old version.” Usually a propagation/cache issue. Wait 5 minutes, hard-refresh. If it persists, ticket support — sometimes server-level config can override.

What’s next

• Adjusting php.ini settings (memory, upload size): MultiPHP INI Editor guide.
• Common php.ini values to tune: Common settings.
• Debug logs to see what changed after a switch: Error logs guide.

MultiPHP Manager handles the basic question of “which PHP runs my site”. For ini settings (memory, upload limits, disabled functions), the companion tool is MultiPHP INI Editor. Together they cover everything CloudLinux’s PHP Selector does — just split across two interfaces instead of one.