SEO · WordPress · Site Recovery

WordPress Recovery:
resolving errors and error states

WordPress powers more websites than any other CMS — but like any software, it can run into errors. This guide covers the most common error states and a practical, step-by-step approach to resolving them without unnecessary panic.

5
most common WordPress error states
FTP
your go-to tool for emergency fixes
404
classic permalink problem
500
internal server error
Basics · Diagnostics

First, identify which error you're seeing

When recovering a WordPress site, the most important thing is not to start randomly deleting plugins, switching themes, or overwriting files. Every error has a different likely cause — the approach for a white screen differs from a database error, which differs again from a permalink problem.

The basic rule is simple: name the error state you see, then take only the action that directly relates to it. Before making any significant change, always make sure you have a current backup of your site.

State 01

White Screen of Death

One of the most feared WordPress errors — instead of your website, visitors see only a blank white page with no error message.

State 02

Database Connection Error

The message "Error establishing a database connection" indicates that WordPress cannot connect to its database.

State 03

Internal Server Error

Also known as a 500 error, this can be caused by a range of issues on the server or configuration side.

State 04

404 Error on Pages

A 404 can appear when visiting pages or posts that exist in WordPress but cannot be found via their URL.

Process · Technical Solutions

WordPress recovery step by step, error by error

Below is a practical overview of the most common WordPress error states. Each step starts with a description of the problem and continues with the recommended technical solution.

01

White Screen of Death (WSoD)

If only a blank white screen appears, connect to your server via FTP, navigate to wp-content/plugins and rename the folder of the plugin you want to deactivate — e.g. from "plugin-name" to "plugin-name-disable". If the issue is memory-related, edit wp-config.php and add: define("WP_MEMORY_LIMIT", "256M");

02

Database Connection Error

For the "Error establishing a database connection" message, check the values DB_NAME, DB_USER, DB_PASSWORD and DB_HOST in your wp-config.php file. Then use phpMyAdmin or another database tool to verify that the server is running and the database contains no errors.

03

Internal Server Error — 500

For a 500 error, access the .htaccess file in your WordPress root directory via FTP. Try temporarily renaming it to ".htaccess_old" and check whether the error disappears. If needed, also increase the PHP memory limit in php.ini or via your hosting control panel.

04

404 Error on Pages and Posts

If an existing page or post returns a 404, go to your WordPress admin under Settings → Permalinks and simply re-save the settings. If the problem continues, check and reset the rewrite rules in your .htaccess file.

05

Errors After Updating WordPress, Theme or Plugins

If an issue appeared after an update, it may be a plugin or theme conflict, or an incomplete system update. Try checking file and folder permissions, or manually update WordPress via FTP by overwriting the core files with the latest version.

Decision Guide · Problem vs. Solution

How to tell where to look first

WordPress errors tend to follow recognisable patterns. You don't need to start with a complex analysis — just match the error state you see to the most likely place where the problem originated.

⚠ Error State

White screen

The site fails to load and visitors see only a blank page with no clear error message.

Database error

WordPress cannot connect to the database or is using incorrect access credentials.

Error 500

The server reports an internal error and cannot process the request correctly.

Error 404

A page or post exists in WordPress but cannot be found via its URL.

✓ First Check

Plugins and PHP memory

Deactivate the problematic plugin via FTP by renaming its folder. Check the memory limit in wp-config.php.

The wp-config.php file

Verify DB_NAME, DB_USER, DB_PASSWORD and DB_HOST. Then check the status of the database server.

.htaccess and PHP limits

Temporarily rename .htaccess and check whether the error disappears. Then address PHP limits if needed.

Permalinks

Re-save permalink settings in the WordPress admin. If that doesn't help, reset the rules in .htaccess.

Summary · Key Takeaways

Key lessons from this guide

Don't panic — don't act randomly

Identify the error type first. White screen, database error and 404 each require a different approach.

wp-config.php is the key file

For database errors, always check the database credentials and host settings here first.

.htaccess resolves a range of issues

For 500 or 404 errors, checking and resetting the rules in .htaccess often clears the problem quickly.

Updates can trigger problems

After updating WordPress, a theme or plugin, it's worth checking compatibility and file permissions.

Backups are the foundation of recovery

Before any major change or update, make sure you have a working backup of your site ready.

Work systematically

One change, check the result, then move to the next step. That way you know exactly what caused — or fixed — the problem.

Ecosystem · Tools and Files

Tools used and recommended resources

Fixing WordPress errors typically involves server access, configuration files and database management. Here are the key tools and concepts referenced in this guide.

FAQ · Frequently Asked Questions

WordPress Recovery: most common questions

What does the white screen of death mean in WordPress?

The white screen of death is a state where only a blank white page appears instead of your website. It is often caused by a plugin, theme, or PHP memory limit issue. The basic approach is to deactivate plugins via FTP by renaming their folder, and optionally increase the memory limit in wp-config.php.

How do I fix a database connection error in WordPress?

First, check the credentials in your wp-config.php file — specifically DB_NAME, DB_USER, DB_PASSWORD and DB_HOST. Then verify that the database server is running and that the WordPress database contains no errors.

What should I do about a 500 error in WordPress?

For a 500 error, check the .htaccess file in your WordPress root directory and try temporarily renaming it to verify whether that resolves the issue. The next step is to check or increase PHP limits via your hosting control panel or php.ini.

How do I fix a 404 error on WordPress pages and posts?

For 404 errors on existing pages, re-saving the permalink settings in the WordPress admin (Settings → Permalinks) usually resolves it. If the problem persists, check and reset the rewrite rules in your .htaccess file.

Need help recovering your WordPress site?

If your site is showing an error, not displaying correctly, or you need advice on WordPress recovery — get in touch. We'll respond within 24 hours and help you get your site back in shape.

Get a free consultation

Free, no-obligation consultation

After you complete the form, we will contact you to arrange a free, no-obligation consultation together. During the consultation, we will discuss your needs and the possibilities for further cooperation. The consultation is completely free and does not commit you to anything.

Quick website analysis

The analysis is prepared manually by our experts within a few business days. You will receive it in PDF format. The analysis is completely free and without obligation. More information can be found here.
Get website analysis