In a cPanel account with CloudLinux PHP Selector enabled, open Select PHP Version, choose a compatible runtime, and apply the change. First check which websites use that selector: an account-level change can affect more than the domain you are working on.
A PHP upgrade can break incompatible application code or extensions. This guide covers preparing the change, checking the effective runtime and recovering if the application fails. It does not assume that every hosting account exposes the same controls.
Before changing a live website
- Record the current PHP version, enabled extensions and custom options. Note every domain sharing that configuration.
- Check your application's and plugins' compatibility requirements. Read the relevant PHP migration guide for changes between the old and intended versions.
- Take a recoverable copy of the application files and database. Confirm how you would restore them; a backup filename alone is not evidence of a working recovery process.
- Test on a separate copy where practical. Keep payments, outgoing email and scheduled integrations from running unintentionally in that copy.
Identify the control that manages the domain
CloudLinux PHP Selector and cPanel MultiPHP Manager are different interfaces. The server's configuration determines which manages a particular site. CloudLinux's PHP Selector documentation shows version, extension and domain controls; cPanel documents its separate MultiPHP Manager.
If both appear, do not change both in the hope that one works. Check the domain's current handler or ask your host which interface is authoritative. If Select PHP Version is absent or the required version is unavailable, ask support about the supported upgrade path.
Apply and verify the change
- Sign in to cPanel and open Select PHP Version, normally under Software.
- Review the domains covered by the setting. Choose the version you have checked against the application's requirements.
- Apply the selection using the confirmation control shown by your installed interface. Older interfaces label this Set as current; wording can vary.
- Review required extensions and options for the selected runtime. Do not assume custom settings were copied from the previous version.
- Check the runtime reported by the application itself, then test login, forms, uploads, checkout where applicable, and scheduled work. A command-line PHP version may differ from the web runtime.
- Review the relevant error logs and keep the previous configuration available during the agreed observation period.
If the site stops working
Return to the previous PHP selection and its recorded options if they remain available, then retest. If code or database changes accompanied the upgrade, changing PHP back may not be sufficient; use the application's documented recovery process and account for data written since the backup.
Give support the domain, change time, old and new versions, affected operation and relevant error message. Do not paste passwords or sensitive customer records into the ticket. Once service is restored, resolve the compatibility problem before attempting the upgrade again. Returning to an obsolete runtime is temporary recovery, not a long-term maintenance plan.
