A blank white page on your WordPress site usually means PHP has hit a fatal error and cannot display anything. This guide walks you through finding the cause and getting your site back online.
Step 1: Enable debug mode
Log in to your Web60 portal and open the site that is showing the white screen. Go to Advanced and turn on Debug Mode. This tells WordPress to record errors instead of silently failing.
Step 2: Reload your site and check for an error message
After enabling debug mode, reload the page that was showing the white screen. In many cases, you will now see a specific error message on screen, such as the name of a file or plugin that caused the crash. Make a note of this — it tells you exactly where the problem is.
Step 3: Check the debug log
If you still see a blank page or the error message is not clear enough, open File Manager in your Web60 portal and navigate to wp-content/debug.log. This file contains a detailed record of every PHP error. Look for the most recent entries — they will reference the file and line number where the crash occurred.
Step 4: Deactivate all plugins
If the error points to a plugin, or if you are not sure what is causing the problem, deactivate all plugins at once using WP-CLI. In your Web60 portal, open the WP-CLI tool and run:
wp plugin deactivate --all --skip-plugins --skip-themes
The --skip-plugins --skip-themes flags tell WP-CLI to bypass loading any plugin or theme code, which is important because the broken code is what is preventing WordPress from running normally.
Reload your site. If it comes back, one of the plugins was the cause.
Step 5: Switch to a default theme
If deactivating all plugins did not fix the issue, the problem is likely your theme. Switch to a default WordPress theme using WP-CLI:
wp theme activate twentytwentyfour --skip-plugins --skip-themes
Reload your site again. If it now loads, your theme was the cause. Contact the theme developer for support or check if a theme update is available.
Step 6: Reactivate one by one
Once your site is loading, reactivate your plugins one at a time. After each activation, reload the site. When the white screen returns, you have found the plugin responsible. You can then look for an update, find an alternative plugin, or contact the plugin developer.
Step 7: Disable debug mode
After you have fixed the issue, go back to Advanced in your Web60 portal and turn off Debug Mode. Leaving debug mode on can expose technical information to visitors and slightly slow down your site.
FAQ
Q: What causes the WordPress white screen of death?
A: It is almost always caused by a PHP fatal error. This means a plugin, theme, or custom code has crashed. The most common triggers are a plugin update that introduced a bug, a theme that is not compatible with your PHP version, or running out of server memory.
Q: Will I lose any content when I deactivate all plugins?
A: No. Deactivating plugins does not delete any data. Your posts, pages, images, and settings all remain in the database. Once you reactivate a plugin, everything will work exactly as before.
Q: How do I know which plugin caused the problem?
A: After deactivating all plugins and confirming the site loads, reactivate them one at a time. Reload the site after each activation. The plugin that brings back the white screen is the one causing the issue.
Frequently asked questions
What causes the WordPress white screen of death?
It is almost always caused by a PHP fatal error. This means a plugin, theme, or custom code has crashed. The most common triggers are a plugin update that introduced a bug, a theme that is not compatible with your PHP version, or running out of server memory.
Will I lose any content when I deactivate all plugins?
No. Deactivating plugins does not delete any data. Your posts, pages, images, and settings all remain in the database. Once you reactivate a plugin, everything will work exactly as before.
How do I know which plugin caused the problem?
After deactivating all plugins and confirming the site loads, reactivate them one at a time. Reload the site after each activation. The plugin that brings back the white screen is the one causing the issue.
Last updated: 4 April 2026