Error 500 and White Screen in WordPress: How to Fix It

Introduction

error 500 (Internal Server Error) and WordPress white screen, known as White Screen of Death or WSOD, are two ways of showing the same type of problem: a PHP failure that prevents WordPress from running correctly.

There is usually a PHP error in the background, but WordPress hides technical messages by default. Depending on the server configuration, the visible result may be a completely blank page or a generic 500 error.

Before making changes, create a backup of your files and database whenever possible. See how to backup and restore WordPress if you don’t have a recent one.

Identify the scope of the problem

Check these addresses:

https://tudominio.com
https://tudominio.com/wp-admin
https://tudominio.com/wp-login.php

Behavior may give a clue:

• Only one page fails: There is usually an error in a template, block, shortcode or specific content.
• The public website fails, but it works /wp-admin: check the theme and the plugins that affect the front.
• The administrator also fails: deactivates plugins from files or database and checks memory.
• Fails only after logging in: There may be a problem with a desktop plugin or a panel customization.

Step 1: Review the error log

The error log usually indicates the file and line that caused the failure.

In DirectAdmin or cPanel, look for sections like Errors, Error Log, or Logs. There may also be a error_log file inside the web folder.

Search for recent messages with expressions like:

PHP Fatal error
Uncaught Error
Allowed memory size exhausted
Call to undefined function
Cannot redeclare

If the error mentions a path within wp-content/plugins/nombre-plugin, that plugin is the prime suspect. If it points to wp-content/themes/nombre-tema, check the active topic.

Step 2: Activate WordPress Debug Logging

If you don’t find enough information, edit wp-config.php and add these lines before the final WordPress comment (you can see the detail in how to activate debug mode):

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

Reload the page that fails and check:

wp-content/debug.log

WP_DEBUG_DISPLAY is kept disabled so that visitors do not see internal routes or technical data. When you are finished, disable debugging (WP_DEBUG in false) and do not leave the debug.log file accessible for longer than necessary.

Step 3: Deactivate all plugins

Plugins are one of the most frequent causes.

If you can log into WordPress: go to Plugins > Installed Plugins, select all and choose Disable in the bulk actions. Check the website and reactivate them one by one until you locate the person responsible.

If you can’t log in: access via FTP or from the file manager, open wp-content and rename the plugins folder to plugins-desactivados. If the website works again, create an empty folder plugins again or return the original name and rename the internal folders one by one until you find the responsible one.

Renaming the folder does not delete the plugin configuration; WordPress will mark them as disabled when it cannot find their files. See how to deactivate WordPress plugins without admin access for more methods, including WP-CLI and phpMyAdmin.

Plugins hosted in wp-content/mu-plugins are loaded automatically and are not deactivated from the normal screen. If the error points to that folder, check its files with caution.

##Step 4: Temporarily change the active theme

If plugins are not the cause, activate a default WordPress theme from Appearance > Themes.

Without administrator access, go to wp-content/themes, check that a default theme exists, and rename the active theme folder. WordPress will try to use another valid theme available. Don’t delete the original theme while testing.

Step 5: Increase available memory

An operation that exceeds PHP’s memory limit may leave the page blank. Add in wp-config.php, before the final comment:

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

These values ​​cannot exceed the maximum limit imposed by PHP or the server. If you need to identify exactly which process is running out of memory, see WordPress memory out of memory.

Step 6: Review an incomplete update

If the error appeared during an update, check if the .maintenance file exists in the WordPress root. If the update has already finished and the website is still under maintenance, delete only that file.

If you suspect corrupted files, download a clean copy of WordPress and replace wp-admin and wp-includes, along with the root files except wp-config.php. Do not replace or delete wp-content.

Step 7: Regenerate .htaccess

A .htaccess file with incorrect rules can cause a server error. Download a copy, rename it .htaccess-anterior and check the website. If you can log in to the administrator, go to Settings > Permalinks and press Save changes to regenerate the rules (see also configure permalinks in WordPress).

This step mainly applies to Apache. In Nginx, rules are managed in the server configuration.

Step 8: Check the PHP version

The white screen may appear after switching from PHP if a plugin or theme uses incompatible code. If the problem started right after updating PHP, temporarily go back to the previous version and update WordPress, the theme and the plugins before trying again. See how to update PHP without breaking WordPress for a safe procedure.

Step 9: Review Permissions and Database

Also check that the folder and file permissions are correct (normally 755 for folders and 644 for files, depending on the server) and that no database tables are damaged. You can check it from phpMyAdmin with the repair tables option, or through a database connection error if the failure seems to be at that point.

Common problems

Change something in functions.php or a child theme

Undo the last change, check braces, parentheses and semicolons, and check for duplicate functions. A single syntax error can prevent WordPress from loading.

The cache still shows the error after solving it

Clear the plugin, server and CDN cache, and test in a private window.

The error appears only on one page

That page may use a template, block or query that causes the failure. The debug log will help locate it.

Frequently asked questions

Does the white screen mean I have lost the website?

Not necessarily. Normally the data continues in the database and the failure prevents WordPress from running or displaying.

Is it safe to activate WP_DEBUG?

Yes, during a controlled review. Save the messages in a file, avoid showing them publicly and deactivate it when finished.

Will restoring a backup solve the problem?

You can fix it if the copy is older than the change that caused the failure. Before restoring, keep a copy of the current state.

When should I hire technical help?

If after checking plugins, theme, memory, PHP and database the problem persists, or if you do not feel comfortable editing wp-config.php or the database.

Conclusion

WordPress error 500 and white screen are usually resolved by locating the error in the logs, deactivating plugins, temporarily changing the theme or correcting the memory and PHP version.

Work step by step and test the website after each change. If you need help, provide support with the error messages and tests performed to speed up the diagnosis.