How to Fix WordPress 500 Internal Server Error & White Screen of Death

Few website errors are as universally dreaded by webmasters as the WordPress 500 Internal Server Error and its silent cousin, the White Screen of Death (WSOD). Unlike typical HTTP errors that provide helpful status codes or explanations, the 500 server error and WSOD give you virtually zero immediate clues. Your site simply refuses to load, showing either an generic browser server error or a stark, blank white screen.

In reality, the 500 Internal Server Error is a catch-all notification indicating that your server encountered an unexpected condition that prevented it from fulfilling the browser’s request. It is almost always triggered by a PHP fatal error, corrupted .htaccess directives, exhausted PHP memory limits, or conflicting plugin scripts. In this comprehensive troubleshooting guide, we walk you through the proven methods to diagnose and resolve 500 errors and the White Screen of Death in 2026.

Step 1: Enable WordPress Debug Mode (Find the Real Error)

Instead of guessing which of your 30 plugins is malfunctioning, let WordPress tell you the exact file and line number causing the crash. Connect to your server using FTP or cPanel File Manager and edit your wp-config.php file.

Find the line that says define('WP_DEBUG', false); and replace it with this complete debugging block:

// Enable WordPress Debug Mode
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Now, refresh your website. WordPress will silently capture all fatal errors and warnings inside a file located at wp-content/debug.log. Open this log file. Look at the very bottom entries for lines starting with PHP Fatal error:. It will show you the exact plugin name and file path responsible for the crash!

Step 2: Check for a Corrupted .htaccess File

A corrupted .htaccess file is one of the most frequent causes of sudden 500 errors. Security plugins, caching rules, or rogue redirect scripts can easily inject faulty syntax into Apache/LiteSpeed configuration files.

1. In your root directory, find the .htaccess file. (Make sure your FTP client has “Show Hidden Files” enabled).
2. Rename the file to .htaccess_old.
3. Refresh your website in your browser. If the site loads normally, you have confirmed that your .htaccess was corrupted!
4. To generate a clean, official WordPress rewrite file, log in to your admin dashboard, go to Settings > Permalinks, and click Save Changes. WordPress will automatically create a brand new, healthy .htaccess file.

Step 3: Increase PHP Memory Limit and Execution Time

When complex themes or plugins (like WooCommerce, Elementor, or LMS platforms) attempt to process large operations, they can exceed your hosting server’s allocated memory threshold, triggering an immediate 500 error or blank page.

Open wp-config.php and add this code:

define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

If you have access to cPanel’s MultiPHP INI Editor, increase your environment variables to these recommended standards:

• memory_limit = 512M
• max_execution_time = 300
• upload_max_filesize = 64M
• post_max_size = 64M

Step 4: Deactivate All Plugins via FTP / File Manager

If a faulty plugin update or code conflict locked you out of the /wp-admin/ panel, you can temporarily deactivate all plugins without touching your database:

1. Connect to your server via FTP or File Manager.
2. Navigate to the wp-content/ directory.
3. Locate the plugins folder and rename it to plugins_deactivated.
4. Refresh your website. If it loads, a plugin was definitely causing the 500 error.
5. Rename the folder back to plugins. Log in to your WordPress admin dashboard, navigate to Plugins, and activate them one by one until the site crashes again. The last activated plugin is your culprit!

Step 5: Re-upload Fresh Core WordPress Files

Occasionally, an automated WordPress core update is interrupted halfway through due to a server timeout, leaving corrupted core PHP files behind.

Download a fresh WordPress zip file from WordPress.org, extract it on your local computer, and upload fresh copies of the wp-admin and wp-includes directories to your server, overwriting existing files. This will restore damaged core system files without touching your themes, uploads, or plugin databases.

If you frequently experience server crashes or database bottlenecks, explore our guide on How to Fix Error Establishing Database Connection, learn how to configure optimal caching in our LiteSpeed Cache Master Guide, and visit the WP Ustaad Resource Hub.