If your WordPress site went blank right after you switched its PHP version in aaPanel, the fastest fix is reverting the PHP version back to what it was — that restores the site immediately in almost every case. Once it's back up, you can switch PHP versions again more carefully by finding out which plugin, theme, or extension actually caused the white screen.

Symptoms

  • The site was working normally, you changed the PHP version in aaPanel's site settings, and now the front end and/or wp-admin show a completely blank white page.
  • No visible error text — just white, in every browser.
  • The white screen appeared immediately after the version switch, not after a plugin update or other separate change.
  • Some sites on the same server (running a different PHP version) are unaffected.

Likely causes, in order of how often they actually happen

  1. A plugin or theme isn't compatible with the new PHP version. Older plugins, custom themes, or anything not actively maintained frequently break on jumps like PHP 7.4 → 8.0/8.1 due to removed or changed PHP language features, and the fatal error is what produces the white screen.
  2. A PHP extension the site depends on isn't enabled for the new version. aaPanel manages PHP extensions per-version — switching versions doesn't carry over which extensions were enabled, so something like imagick, mbstring, or redis can be missing on the new version even though it was enabled on the old one.
  3. The new PHP version's default settings differ enough to expose a latent bug in custom code (a theme's functions.php, for instance) that happened to work under the old version's more lenient error handling.

Fix it: lowest-risk steps first

Step 1 — Revert the PHP version immediately

In aaPanel, go to Website → your site → Settings (or the site list's PHP version dropdown directly), and switch the PHP version back to whatever it was running before. This is non-destructive and takes effect in seconds — it doesn't undo anything else, it just restores the exact runtime the site was already working under.

Confirm the site loads normally again before doing anything else. If it doesn't come back after reverting, the white screen wasn't actually caused by the PHP version switch — treat it as a separate issue (check the PHP-FPM error log under Website → Log for a fatal error unrelated to PHP version).

Step 2 — Enable WP_DEBUG to see what actually broke

With the site back on the working PHP version, you can now safely investigate the new version in a lower-risk way. Edit wp-config.php via aaPanel's file manager and set:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

This logs errors to wp-content/debug.log without displaying them to visitors. Switch the PHP version forward again to the new one, reload the site once (it'll still white-screen), then check debug.log for the specific fatal error — it will typically name a plugin file, a theme file, or a specific missing function/class.

Set WP_DEBUG back to false once you've captured the error, and switch back to the working PHP version if you're not ready to fix the cause yet.

Step 3 — Check whether the new PHP version has a required extension disabled

In aaPanel, go to App Store → PHP for the new version → Settings (or Install extensions, depending on your aaPanel version) → the extensions/modules tab. Compare which extensions are toggled on there against the version you reverted to. Common ones WordPress sites depend on that don't always carry default-enabled across versions: imagick, redis or memcached (if you use object caching), mbstring, exif, and zip.

If debug.log from Step 2 mentioned a missing class or function tied to one of these (for example, an Imagick class error), enable the matching extension for the new PHP version and restart PHP-FPM from the same settings tab. Then switch the site to the new version again and retest.

Step 4 — Identify and update or replace the incompatible plugin/theme

If debug.log names a specific plugin or theme file rather than a missing extension, that component needs updating for the new PHP version, or temporarily deactivating. With the site on the working PHP version, go to wp-admin → Plugins and check if an update is available for the named plugin — many plugin authors ship PHP 8.x compatibility fixes as a routine update. If no update exists or the theme itself is the problem, deactivate that plugin (or switch to a default theme like Twenty Twenty-Four temporarily) before switching PHP versions again, then reintroduce it once you've confirmed the base site handles the new version fine.

Verify the fix

  1. With the target PHP version active, load the front end and wp-admin in a private window and confirm normal rendering, not a blank page.
  2. Check wp-content/debug.log (if you left logging on temporarily) for any remaining warnings, and turn WP_DEBUG back off once clean.
  3. Click through a few key pages and any custom functionality (contact forms, page builder content) to confirm nothing is silently broken even though the white screen is gone.

If you need to roll back

If the new PHP version still isn't stable after Steps 3 and 4, there's no penalty to simply staying on the older, working PHP version in aaPanel until you have time to update the offending plugin or theme properly — older PHP versions remain fully functional in aaPanel's App Store even if they're not the newest available. If a plugin deactivation in Step 4 caused a different problem (missing functionality), reactivate it and restore the plugin's data from the backup taken at the start rather than troubleshooting two changes at once.

Related fixes

FAQ

Why does aaPanel let me switch to a PHP version that breaks my site?

aaPanel manages the PHP runtime itself, not the compatibility of the WordPress plugins and themes running on it — that's outside what the panel can check. The version switch itself always succeeds technically; whether your specific site's code is compatible with that version is a separate question aaPanel has no way to verify in advance.

Is it safe to just stay on an older PHP version instead of fixing this?

For a while, yes — but older PHP versions eventually stop receiving security updates upstream, so treat this as a deadline rather than a permanent solution. Use the extra time to update or replace the incompatible plugin, then retry the switch.

Does switching PHP versions in aaPanel affect the WordPress database or files?

No — the PHP version is purely the runtime that executes your site's code; it doesn't touch the database, uploads, or plugin/theme files at all. That's exactly why reverting it in Step 1 is safe and instant — you're not undoing any data changes, only switching which PHP engine runs the same unchanged files.