Quick answer: Set PHP per site in your panel: CloudPanel site settings (PHP version dropdown), cPanel MultiPHP Manager, HestiaCP domain → Advanced → PHP version (with the php-fpm template), CyberPanel website → Change PHP, aaPanel site → PHP version. Keep production on a currently supported PHP (8.2/8.3) and test upgrades on a staging copy first.
Overview
Different apps need different PHP versions, and PHP releases go end-of-life every year — running an unsupported PHP is both a security and performance problem. Panels install multiple PHP-FPM versions side by side and let each site pick its own, so you can upgrade sites one at a time.
Before you start
- Know your app's supported PHP range (WordPress core currently runs great on PHP 8.2/8.3; old plugins may lag).
- A recent backup — a PHP switch is instant, but app breakage is possible.
Step-by-step guide
- Install the additional PHP version if the panel does not have it yet (cPanel: WHM MultiPHP; aaPanel/CyberPanel: App Store / PHP section; CloudPanel and HestiaCP ship several by default).
- Switch the site's PHP version in the panel (menu paths in the Quick answer).
- Install any missing PHP extensions for that version (each version has its own extension set).
- Reload the site and test the critical paths: login, checkout, admin pages, cron/CLI tasks.
- If something breaks, switch back — versions coexist, so rollback is one click.
Common issues
- 500 after switching: a missing extension (e.g.
intl,gd,mbstring) for the new version — install it and reload PHP-FPM. - CLI still uses old PHP: the shell default differs from the site's FPM version — call the versioned binary (e.g.
php8.3) in cron jobs. - Deprecation warnings flood logs: the app predates the PHP version — update the app before forcing new PHP.
- Different php.ini limits: memory/upload limits are per version — re-apply your overrides after installing a new one.
When to contact support
App-level PHP errors on an unmanaged server are on the application side, but if PHP-FPM itself will not start or the panel's PHP packages are broken at the OS level, open a support ticket with the error output.
Frequently asked questions
Which PHP version should I run in production?
A currently supported branch — PHP 8.2 or 8.3 for most apps today. Older branches stop receiving security fixes, so plan upgrades before your version reaches end of life.
Can different sites use different PHP versions?
Yes. Panels install PHP-FPM versions side by side and let each site select its own, so you can upgrade sites one at a time without touching the others.
Why did my site break after a PHP upgrade?
Most often a missing extension for the new version or deprecated code in an old plugin/theme. Install the extensions, check the error log, and roll back with one click if needed.
Related articles
- How to create a website in a control panel
- How to create a database
- Common control panel installation errors
Need a hand? Contact Cloud2Y support →
