MultiPHP vs CloudLinux PHP Selector – Which You Have

Customers with hosting on multiple iWebVault servers notice that PHP management looks different from server to server. On some, you see Select PHP Version with per-account extension toggles. On others, you see MultiPHP Manager and MultiPHP INI Editor, with no extension toggle UI. The difference comes down to whether the server runs CloudLinux. This guide explains the distinction, what changes, and how to work effectively with either.

CloudLinux at a glance

CloudLinux is a Linux distribution optimized for shared hosting. It adds:

• LVE (Lightweight Virtual Environment) — per-user CPU, memory, and I/O limits enforced at kernel level.
• CageFS — file system isolation so each user only sees their own files.
• PHP Selector — per-user PHP version + extension toggles.
• HardenedPHP — security patches for end-of-life PHP versions.

Most iWebVault shared hosting runs on CloudLinux for the isolation and per-user control benefits. A few servers don’t — those use stock AlmaLinux/RHEL.

How to tell which you have

Open cPanel → Software section.

Feature comparison

Where settings actually live

CloudLinux PHP Selector

• Per-user ini: /etc/cl.php.d/alt-phpXX/alt_php.ini
• Selector state: /etc/cl.selector/
• Effective via CageFS — the user’s environment shows just their values.

cPanel MultiPHP

• System ini: /opt/cpanel/ea-phpXX/root/etc/php.ini
• cPanel-edited overlay: /opt/cpanel/ea-phpXX/root/etc/php.d/zzcustom.ini or similar
• Affects all users on the server.

Important: on CloudLinux servers, editing system-level php.ini doesn’t reach end users at runtime because PHP Selector overrides at the per-user level. To actually change a user’s php.ini on CloudLinux, use Select PHP Version → Options.

Migrating between server types

Sometimes accounts move between servers — load balancing, hardware upgrade, server consolidation. If you’ve moved from a CloudLinux server to a non-CloudLinux one (or vice versa), expect:

CloudLinux → non-CloudLinux

• Your per-account extension preferences don’t carry over (extensions become server-wide).
• If you’d disabled extensions for security on the old server, you can’t disable them per-account on the new one — they’re either installed or not.
• Your custom ini values may not transfer — set them again via MultiPHP INI Editor or .user.ini.
• If you were on a HardenedPHP-supported old PHP version (5.6, 7.0), upgrade — these aren’t available on non-CloudLinux servers.

Non-CloudLinux → CloudLinux

• You gain per-account control via PHP Selector.
• Per-domain MultiPHP Manager settings carry over.
• Most extensions installed on the old server are also available; some niche ones may differ.

When we migrate accounts, we try to preserve PHP version and key settings. Verify after migration via phpinfo.

Practical recommendations by server type

On CloudLinux servers

• Use Select PHP Version (the CloudLinux PHP Selector UI) for everything PHP-related.
• Set ini values via Options tab.
• Disable extensions you don’t need (small security gain).
• disable_functions configurable per-account here.

On non-CloudLinux servers

• Use MultiPHP Manager for PHP version selection.
• Use MultiPHP INI Editor for ini values.
• Apply 7-function disable_functions hardening per hardening guide.
• For per-domain overrides, use .user.ini in the domain’s document root.
• If a needed extension is missing, ticket support.

If unsure which you’re on

Check phpinfo. Look at “Server API” near the top — both setups can run FPM or LSAPI. Then look for:

• CageFS or alt-php references — you’re on CloudLinux.
• No such references — non-CloudLinux.

Or just open a ticket — “Which PHP management system is on my hosting?” — we’ll confirm.

Common questions

“Can I request CloudLinux on my server?” CloudLinux is a per-server install decision, not something individual accounts can opt into. If you want CloudLinux specifically, ask sales for plans on CloudLinux servers.

“My old hosting had PHP 5.6 – why isn’t it here?” PHP 5.6 is end-of-life. CloudLinux’s HardenedPHP keeps it security-patched; standard cPanel servers don’t. Upgrade your code to PHP 8.x — 5.6 hasn’t received official security patches since 2018.

“Extensions list looks different than my last host.” Different servers have different builds. The common ones are universally available; specialty extensions vary. Open a ticket if something specific is missing.

“I prefer the PHP Selector UI; can I have that on a non-CloudLinux server?” No — PHP Selector requires CloudLinux. The MultiPHP tools provide the same capabilities, just through a different UI.

“Does any of this affect site performance?” Not materially. Both setups run PHP-FPM or LSAPI handlers with similar performance characteristics. CloudLinux’s LVE adds slight overhead in exchange for isolation; on a properly sized server, you won’t notice.

What’s next

• If on non-CloudLinux: MultiPHP Manager, MultiPHP INI Editor.
• If on CloudLinux: PHP version settings (CloudLinux).
• Per-domain overrides work on both: .user.ini.
• Security hardening: disable_functions.

Both systems do the same job through different interfaces. CloudLinux’s PHP Selector is friendlier for end users — extension toggles in particular. cPanel’s native MultiPHP requires ticket coordination for extension changes but is otherwise equally capable. Match your workflow to whichever your server uses; both reach the same outcomes.