Troubleshooting Common WordPress Errors for Beginners

Last updated: November 6, 2026 · By Ryan Walsh

Most WordPress errors have a small set of causes, and you can usually find the fix by identifying the error message and changing one thing at a time. This guide explains the most common errors beginners face, what each one usually means, and which checks to run first. If you follow the steps in order, you can narrow down the cause without guessing.

Troubleshooting WordPress errors works best when you record what changed before the problem started. A new plugin, a theme update, or a PHP version change is the most common trigger. Keep a backup of your site before you touch any files.

Key Takeaways

• The white screen of death can be caused by either PHP errors or database errors, and it displays a blank page with no error message.
• The WP_DEBUG_LOG setting does nothing unless WP_DEBUG is also set to true in wp-config.php.
• Most “Error Establishing Database Connection” messages come from incorrect database name, username, password, or host values in wp-config.php.
• Folder permissions of 755 and file permissions of 644 are the usual starting point for the wp-content/uploads directory.
• You can find a plugin conflict in a few minutes by deactivating all plugins and reactivating them one at a time.

How do you start troubleshooting WordPress errors?

Start by writing down the exact error message, when it began, and what you changed just before. Then make a backup and work through the checks below in order. Most issues become clear once you know the message and the recent change.

1. Back up your files and database before changing anything. Our guide to WordPress backup plugins explains how to set one up.
2. Note the exact error text, including any file name and line number it shows.
3. Undo the most recent change, such as a plugin install, theme switch, or update, and check whether the site recovers.
4. Turn on debugging to reveal hidden details (see the parse error section below).
5. Check your host’s error logs, which often record the exact file causing the failure.

What do common WordPress error messages mean?

Each common error points to a specific family of causes, so matching the symptom to the table below is the fastest way to choose a fix. Use the first fix as your starting point, then move to the matching section for detailed steps.

How do you fix the white screen of death?

The white screen of death is a blank page with no message, and it usually means PHP or database code failed before the page could load. According to the WordPress Developer Handbook’s list of common errors, it can be triggered by either PHP errors or database errors. Because the page gives no clues, you need to turn on debugging to see what is failing.

Steps to recover from a white screen

1. Enable debugging in wp-config.php, as described in the parse error section below, and reload the page.
2. If you are locked out of wp-admin, connect by FTP or your host’s file manager and rename the plugins folder in wp-content to plugins-off. This disables all plugins at once.
3. If the site returns, rename the folder back and reactivate plugins one at a time to find the one that fails.
4. If plugins are not the cause, switch to a default theme by renaming your active theme folder in wp-content/themes.
5. If the error mentions memory, raise the memory limit as described in the memory section below.

If none of these steps work, contact your host with the debug log contents. The log will show the file and line where the failure occurs.

What causes a 500 Internal Server Error, and how do you fix it?

A 500 Internal Server Error means the server ran into a problem it could not handle, and WordPress shows only a generic message. Common causes include a corrupted .htaccess file, a plugin conflict, or a PHP memory limit that is too low. Work through the fixes below from the simplest to the most involved.

1. Rename your .htaccess file to .htaccess-old using FTP or your host’s file manager. Then load your site.
2. If the site loads, go to Settings, then Permalinks, and click Save Changes. WordPress will generate a new .htaccess file.
3. If the error remains, deactivate all plugins using the plugins-folder method described above.
4. Check the PHP version in your hosting control panel and make sure it is supported by your WordPress version.
5. Look in your server error log for a specific file name, which points you to the cause.

If the 500 error continues after these steps, ask your hosting provider to check server-level logs. They can see problems you cannot access from wp-admin.

How do you fix the Error Establishing Database Connection?

This message means WordPress cannot connect to its database, and the most common reason is incorrect credentials in wp-config.php. Check the four database values against the details your host gave you. A single typo in any of them will cause this error.

• DB_NAME: The database name must match exactly what your host created.
• DB_USER and DB_PASSWORD: Confirm the username and password for typos, extra spaces, or old values.
• DB_HOST: Most shared hosts use localhost, but some use a separate server name. Use the value your host provides.

If the credentials are correct, the database server may be down or overloaded. Contact your host, since they can check the server status. If the database itself is corrupted, you can add define(‘WP_ALLOW_REPAIR’, true); to wp-config.php, then visit yoursite.com/wp-admin/maint/repair.php. Remove that line once the repair finishes, because the repair page does not require a login.

How do you fix parse errors and syntax mistakes?

A parse error means PHP cannot read a line of code, usually because of a missing semicolon, unmatched bracket, or unclosed parenthesis. The error message names the file and line number, which tells you exactly where to look. Fixing the code at that line usually restores the site immediately.

Common syntax problems include:

• Missing semicolons at the end of a statement
• Unmatched curly brackets { } in a function
• Unclosed parentheses in a function call
• Stray characters pasted in from a web page or word processor

How do you turn on WordPress debugging safely?

Debugging mode displays and records errors that WordPress would otherwise hide. Open wp-config.php and add these lines above the line that reads “That’s all, stop editing!”:

• define(‘WP_DEBUG’, true);
• define(‘WP_DEBUG_LOG’, true);
• define(‘WP_DEBUG_DISPLAY’, false);

WordPress writes errors to wp-content/debug.log when logging is on. As the WordPress debugging guide explains, WP_DEBUG_LOG has no effect unless WP_DEBUG is also set to true. Turn debugging off once you have fixed the problem, and avoid editing live theme files directly, since a child theme protects your changes during updates.

How do you fix memory limit errors?

Memory limit errors appear as “Allowed memory size of X bytes exhausted” and usually occur during heavy tasks such as image processing or large imports. They happen when PHP reaches its memory cap before the task finishes. Raising the limit or removing the process that uses the most memory will fix most cases.

1. Open wp-config.php and add define(‘WP_MEMORY_LIMIT’, ‘256M’); above the “stop editing” line.
2. Reload the page. If the error persists, ask your host whether a higher PHP memory limit is available on your plan.
3. Deactivate plugins you do not use, since poorly optimized plugins are a frequent cause of heavy memory use.
4. If long scripts time out, ask your host to increase max_execution_time, which often defaults to 30 seconds.

Note that some hosts ignore the WP_MEMORY_LIMIT setting if the server limit is lower. In that case, the host must change the server setting.

How do you fix login problems and forgotten passwords?

To recover a forgotten password, click the “Lost your password?” link on the login page and follow the reset email. If you are locked out for another reason, such as a security plugin or a broken plugin, you can disable the plugin through FTP without touching your content.

What do you do if the reset email never arrives?

Check your spam folder first, then confirm the email address on your account matches the one you are using. If the email still does not arrive, your server may not be sending mail, which is covered in the email section below. Your host can also reset the password for you.

1. Use an FTP client or file manager to open wp-content/plugins.
2. Rename the security plugin’s folder so WordPress disables it.
3. Log in and reset your password, then rename the folder back and reactivate the plugin.

If you have command-line access, WP-CLI can change a password directly with the command wp user update your-username –user_pass=NewStrongPassword. This avoids editing the database by hand, which is risky for beginners.

How do you fix plugin and theme conflicts?

A plugin or theme conflict happens when two pieces of code change the same feature, which can break your layout, cause redirect loops, or block your dashboard. The fastest way to find the culprit is to disable everything and turn plugins back on one by one. Do this on a staging copy if your site is live and busy.

1. Clear your browser cache and cookies, since stale session data can mimic a conflict.
2. Deactivate all plugins from wp-admin, or rename the plugins folder if you cannot log in.
3. Check the site. If it works, reactivate plugins one at a time, loading the site after each one.
4. When the problem returns, you have found the conflicting plugin. Update it, replace it, or contact its developer.

If WordPress detects a fatal error, recent versions can send an email to the site admin address with a link to recovery mode. That link lets you deactivate the problem plugin without logging in normally. Also make sure your WordPress Address and Site Address settings in Settings, then General, are correct, since a mismatch can cause redirect problems.

How do you fix image upload errors?

Image upload errors usually come from folder permissions, PHP upload limits, or a full disk. The message “Upload failed: Unable to write file to disk” most often means WordPress cannot write to the uploads folder. Check permissions and storage before changing any other setting.

• Set folders in wp-content/uploads to 755 and files to 644.
• Confirm your host plan has enough free storage for your media files.
• Set upload_max_filesize and post_max_size in php.ini or your host’s PHP settings to a value larger than your biggest file.
• Compress images before uploading and use JPG, PNG, or GIF formats.

For the full media workflow, see how the WordPress Media Library handles file storage and organization.

Why are WordPress emails not sending?

WordPress sends email through PHP’s mail function by default, and many hosts block or throttle that function, so messages never arrive. An SMTP plugin fixes this by sending mail through an authenticated mail server. WP Mail SMTP is a widely used option for beginners.

• Enter the SMTP server address, port, username, and password from your email provider.
• Send a test email from the plugin’s settings page.
• Check the plugin’s email log for bounces or spam-filter rejections.

How do you fix 404, 403, and redirect errors?

A 404 error means the URL does not match any page, a 403 error means the server is blocking access, and a redirect loop means two rules keep sending the browser back and forth. Each has a different cause, so identify which one you see before you fix it.

• 404 errors: Save your permalinks again in Settings, then Permalinks. If you moved content, add a redirect with a redirection plugin. Google Search Console’s indexing reports list pages returning errors.
• 403 errors: Check file permissions and any security plugin rules that block your IP address or specific pages.
• Too Many Redirects: Confirm the WordPress Address and Site Address match your intended URL, then clear your browser cache and cookies.

If you need to manage who can access the dashboard, our article on how to manage WordPress user roles and permissions explains how to set access levels correctly.

How do you get out of maintenance mode?

To leave maintenance mode, delete the .maintenance file from your site’s root folder using FTP or your host’s file manager. WordPress creates this temporary file when an update starts, and an interrupted update can leave it behind. Once it is removed, your site should return to normal.

1. Connect to your site by FTP or SFTP.
2. Go to the root folder where wp-config.php is located.
3. Delete the file named .maintenance.
4. Reload your site and check that it works, then run any pending updates again.

How do you fix RSS feed XML errors?

RSS feed errors usually come from XML formatting problems, such as extra whitespace, unescaped characters, or an unclosed tag in a theme or plugin. Validating the feed will show the exact line that is wrong. Fix that line in the source file, then validate the feed again.

Use an online feed validator, such as the W3C Feed Validation Service, to check your feed’s structure. Re-validate after you update a theme or plugin, since those updates can introduce new formatting errors.

When should you contact your hosting provider?

Contact your host when you cannot find the cause in your site’s files or when the error points to the server itself. Hosts can read server logs, check resource limits, and confirm database health. Provide the exact error text and any debug log entries to speed up their response.

• The 500 error persists after you rename .htaccess and deactivate plugins.
• The database connection fails even though your credentials are correct.
• You need a higher PHP memory limit or upload size than your plan allows.
• Your email and recovery methods have failed, and you need the password reset done for you.

Frequently Asked Questions

What is the first thing to do when my WordPress site breaks?

Make a backup of your files and database before you change anything, even if the site looks broken. Then note the exact error message and what you changed most recently. Undoing that last change is often the quickest way to restore the site.

How do I find the exact cause of a WordPress error?

Turn on WP_DEBUG and WP_DEBUG_LOG in wp-config.php, then reproduce the error. The log in wp-content/debug.log records the file and line number. Check your host’s error logs as well if the debug log is empty.

Can a plugin break my whole WordPress site?

Yes, a plugin can cause a white screen, a 500 error, or a blocked dashboard, especially if it conflicts with another plugin or your theme. You can disable all plugins at once by renaming the plugins folder in wp-content. Then reactivate them one at a time to find the one causing the problem.

Is it safe to leave debug mode turned on?

It is safe on a local or staging site, but you should turn it off on a live site after you fix the problem. Setting WP_DEBUG_DISPLAY to false keeps error messages off the public page while still logging them. Remove the logging lines when you no longer need them.

What should I do if I get locked out of WordPress?

Use the Lost your password link first, and check your spam folder for the reset email. If that fails, disable a security or problem plugin through FTP, then log in and reset your password. Your host can also help if you cannot access the files.

Conclusion

Troubleshooting WordPress errors becomes manageable when you read the message, back up your site, and change one thing at a time. Start with the quick reference table, then follow the matching section to test the most likely fix. Keep your WordPress core, themes, and plugins updated, and your site will be easier to keep running smoothly.