Confirm root-level authorisation, a current server recovery plan and the application’s supported PHP versions. Record the existing EasyApache packages and export the current configuration as a profile.

1. Open EasyApache 4 and choose Customize for the currently installed package set.
2. In the PHP Versions section, select the supported additional runtime. Review the offered extension set instead of assuming every required extension will be included.
3. Keep existing runtimes needed by other accounts selected. Continue to the review screen and inspect installs, upgrades and removals carefully.
4. Provision the approved change and wait for completion. Save the build result and investigate any package errors.
5. Use MultiPHP Manager to assign the new version to an isolated test domain first. Verify application functions and the effective web runtime before scheduling production changes.

The additional PHP version should appear as an available supported option, while unrelated domains retain their intended runtime. Check scheduled CLI jobs separately because their PHP executable can differ.

If provisioning proposes removing a required runtime or module, stop and review the profile selection. Do not install an arbitrary operating-system PHP package over the managed EasyApache stack. A legacy runtime requires a separate supported security-maintenance decision.

Installation and domain assignment are different operations. Check default and inherited settings before changing them, because a global-default change can affect domains that inherit that version.

• Adding an EasyApache PHP extension without changing every domain
• Enabling PHP-FPM for a domain and checking shared document roots
• Choosing the correct PHP executable for a cron job
• Planning a supported database-server upgrade from WHM

• cPanel: Easyapache 4 Interface
• cPanel: Multiphp Manager For Whm