A blank white page, "There has been a critical error on this website", or a "500 Internal Server Error" all usually mean the same thing: a PHP error stopped WordPress before it could finish loading. In most cases a plugin, theme or recent update is to blame. This guide shows how to find the cause and fix the WordPress white screen and 500 errors on an Instant Access Internet Services site, starting with the quickest checks.
Before you start
- Think about what changed just before the problem: a plugin or theme update, a new plugin, a PHP version change, or an edit to a file. That's the most likely cause.
- Check the email address of your WordPress admin account. WordPress often sends an email titled something like "Your Site is Experiencing a Technical Issue" with the name of the plugin or theme that failed and a special recovery mode link.
Step 1: Use WordPress recovery mode (if you got the email)
- Before using the recovery mode link in the email, check it's genuine: it should come from your own site, arrive right after the error started, and point to
wp-login.phpon your own domain. If anything looks off, don't click it; skip to Step 2 instead. (We normally say never to click links in emails. This is the one exception, and only after those checks. See WordPress Critical Error on This Website: How to Fix It.) - Log in. WordPress shows which plugin or theme caused the error and pauses it for you.
- Go to Plugins (or Appearance > Themes), deactivate the problem plugin or switch themes, then click Exit Recovery Mode.
Step 2: Find the error message in the logs
The exact error tells you which file and plugin are at fault.
- In cPanel, go to Metrics > Errors to see the latest web server errors for your site.
- In Files > File Manager, look for a file named
error_loginpublic_htmlor inwp-admin. Open it and scroll to the bottom for the newest entries.
Look for a line starting with PHP Fatal error. A path such as wp-content/plugins/some-plugin/... points straight to the culprit.
If you don't find anything, turn on WordPress debug logging. Edit wp-config.php in File Manager and add these lines just above the line that says /* That's all, stop editing! */:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );
Reload your site, then open wp-content/debug.log. When you've fixed the problem, set WP_DEBUG back to false and delete debug.log.
Step 3: Disable all plugins without logging in
- In File Manager, open
public_html/wp-content. - Rename the
pluginsfolder toplugins.off. - Reload your site. If it works now, a plugin was the cause.
- Rename the folder back to
plugins. WordPress will list all plugins as deactivated. - Log in to WordPress and reactivate plugins one at a time, reloading the site after each, until the error comes back. Leave that plugin off and look for an update or replacement.
If the error message named a specific plugin, you can skip the testing and just rename that plugin's folder inside wp-content/plugins.
Step 4: Switch to a default theme
If disabling plugins didn't help, the theme may be at fault. In wp-content/themes, rename your active theme's folder (for example add .off to the end). WordPress falls back to a default theme such as Twenty Twenty-Five if it's installed. If the site loads, the theme needs updating or fixing.
Step 5: Other common causes
| Error in the log | What to do |
|---|---|
Allowed memory size of ... bytes exhausted | Raise memory_limit in Software > MultiPHP INI Editor (the default is 128M; 256M is plenty for most sites). See the PHP settings guide below. |
Call to undefined function or syntax errors after a PHP change | A plugin or theme doesn't support your PHP version. Update it, or switch back to the previous PHP version in Software > MultiPHP Manager while you sort it out. |
Errors mentioning .htaccess, or 500 errors on every page with nothing in the PHP logs | Rename .htaccess in public_html to .htaccess.off. If the site works, log in and go to Settings > Permalinks and click Save Changes to create a fresh one. |
| You edited a theme file just before the crash | Undo your edit in File Manager, or restore that file with JetBackup 5. |
| Nothing obvious, and Resource Usage shows limit hits | The site ran out of CPU or processes. Turn on LiteSpeed Cache and look for heavy plugins. |
Still broken? Restore a backup
If you can't find the cause, restore the site to the last time it worked: use a WP Toolkit backup, or restore files and database from our automatic backups in JetBackup 5.
If you open a ticket, include the exact error message from the log and what changed before the problem started. That lets us help you much faster.
Related guides
- How to Check Your Website Error Log and Recent Visitors
- How to Change PHP Settings (memory_limit, upload_max_filesize)
- How to Change Your PHP Version in cPanel
- How to Show Hidden Files (.htaccess) in cPanel File Manager
- How to Back Up and Restore WordPress in WP Toolkit
Still stuck? Open a support ticket and the Instant Access Internet Services team will help.
