If I had to guess, you’re here because your website just encountered one of the common WordPress errors, and you’re looking for a fix that will help restore things as quickly as possible. Well, don’t worry, we’ve got you covered!

In this article, we’ll help you understand the reason behind the WordPress error you’re facing and share the best solutions. Once you implement them, your site should be back up and running in no time.

The Easy Way to Find and View WordPress Errors

Every time an error occurs on your WordPress site, resolving it quickly should be your top priority. WordPress debugging plugins make this process much easier by helping you pinpoint exactly what caused the issue.

WP Debug Toolkit is the most user-friendly debugging plugin for WordPress users who want to troubleshoot errors efficiently.

With WP Debug Toolkit, you can enable debug mode and error logging through a user-friendly interface, without editing the wp-config.php file manually. Using the log viewer app, you can see all WordPress and PHP errors on your site, organized by log level, including Notice, Fatal, Warning, Parse, and Error.

For each error, you can explore further with the file viewer to see the full context, including the exact file and line number where the error occurred.

Keyboard shortcuts are also available to help you navigate the app and find errors more quickly.

1. 500 Internal Server Error 

If you just encountered the 500 Internal Server error on your website, then it means that your server has run into a situation where it cannot complete a request for unexpected reasons. In essence, it happens when an HTTP request fails. 

The 500 internal server error may display with different codes, such as “500 Error”, “HTTP 500”, “500. That’s an error”, or “500 Internal Server Error, Sorry something went wrong”. Some of the leading causes of the 500 Internal Server Error include a corrupt .htaccess file, corrupted browser cache files, conflicts with WordPress themes and plugins, incorrect file and folder permissions, database server issues, corrupted WordPress core files, and memory limitation issues, among others.

Internal Server Error (500) Fix

1. Reload the web page: Sometimes, all you need to do to fix the 500 Error is wait a few minutes and refresh the page.
2. Regenerate .htaccess file: If you can access your admin dashboard, go to Settings › Permalinks in your WordPress admin dashboard and click the Save Changes button without making any changes to regenerate .htaccess file if it’s been corrupted. Alternatively, you can manually regenerate the file in cPanel or via FTP by navigating to /public_html/, locating it, renaming it, and creating a new file with fresh .htaccess code.

3. Increase PHP Memory Limit: Update the memory limit in your site’s wp-config.php or php.ini file by adding the line: define('WP_MEMORY_LIMIT', '256M');. You can also do this using a code snippet plugin like WPCodeBox.
4. Clear your browser cache: Go to your browser settings and clear your website’s cache to remove any corrupted files that may be triggering the error.
5. Deactivate your plugins and themes: If the error is caused by conflicting plugins or a poorly coded theme, deactivate and reactivate them one by one to find the culprit.

Other steps include checking file and folder permissions, examining server logs, reinstalling WordPress core files, and consulting your hosting provider about potential server issues.

2. Error Establishing a Database Connection

When your website can’t connect to the WordPress database, it displays the message “Error Establishing a Database Connection.” The database holds most of your site’s data, except for media files and core, theme, or plugin files. Therefore, if your website cannot connect to the database, no data will be shown.

The primary cause of this error is incorrect database login credentials. Corrupted database files can also lead to this issue. 

Other causes include hosting server problems, corrupted WordPress core files, and traffic spikes.

Error Establishing a Database Connection Fix

1. Verify database login credentials: Access your File Manager and open the wp-config.php file to check if the database name, MySQL username, MySQL password, and hostname (server) are correct.

2. Check if the database server is down: Confirm whether your database server is offline by checking your hosting dashboard or reaching out to your hosting provider.
3. Repair corrupted database files: Enable WordPress’s built-in database repair mode by adding ‘define('WP_ALLOW_REPAIR', true);‘ to your wp-config.php file.
4. Fix corrupted WordPress core files: Backup your site, download a fresh copy of WordPress, delete the /wp-content/ folder and the wp-config-sample.php file, then upload the remaining files via FTP to replace any corrupted files.

3. White Screen of Death

If your WordPress site suddenly appears blank without any error message, you’ve encountered the White Screen of Death.

In WordPress 5.2 or later, this error typically shows a message like “There has been a critical error on this website. Please check your site admin email inbox for instructions,” or “This site is experiencing technical difficulties.”

The main causes of the White Screen of Death include PHP memory limit exhaustion, plugin compatibility issues, corrupted WordPress core files, and a faulty theme.

White Screen of Death Fix

1. Deactivate the faulty plugin through Recovery Mode: If you receive an email from WordPress when encountering the White Screen of Death, use the information and the recovery mode link provided to deactivate the plugin that caused the problem.

2. Deactivate all plugins: If you don’t receive an email, you can instead access your File Manager through cPanel or FTP and go to the /wp-content/ folder. Find the plugins folder and rename it to disable all plugins on your site. If the White Screen of Death disappears, it indicates a plugin issue. Reactivate the plugins one by one to identify the culprit.

3. Activate the default WordPress theme: Use FTP to go to /wp-content/themes/. Right-click on your current theme and select delete. This will immediately switch your site to the default WordPress theme, which should fix the issue if it’s related to the theme.
4. Increase the PHP memory limit: Edit your wp-config.php file or use a code snippet plugin like WPCodeBox to add the code define('WP_MEMORY_LIMIT', '512M');. This should increase your site’s PHP memory limit.
5. Repair corrupted WordPress core files: The steps for this process are outlined here. 

4. 404 Page Not Found Error

The 404 Page Not Found error occurs when a page on your website is missing from the URL a visitor enters in their web browser.

Why does this happen? Several reasons include: the page may have been moved or deleted, you might have mistyped the URL, you may have changed your permalink structure (which can lead to broken links), your .htaccess file could be corrupted, or your domain name might not be correctly pointed to the web server.

404 Page Not Found Error Fix

1. Check the URL for typos: Verify that the URL entered is free of spelling mistakes or missing characters.
2. Check your DNS settings: If the 404 error occurs because your domain isn’t pointed correctly, go to your domain provider’s control panel and ensure that the correct nameserver information has been entered to fix the error.

3. Regenerate the .htaccess file: Follow the steps outlined here to easily regenerate your .htaccess file.
4. Set up URL redirects: Use a plugin like Yoast SEO to create URL redirects for pages that have been deleted or moved. This helps prevent visitors from encountering a 404 error after internal changes.

5. “ERR_CONNECTION_TIMED_OUT” Error

The “ERR_CONNECTION_TIMED_OUT” error, or “cURL error 28: Connection timed out” error, occurs when a web server takes too long to respond to a web page request. It is quite common on websites using shared hosting plans with limited resources.

The main causes of the “ERR_CONNECTION_TIMED_OUT” error include a poor internet connection, an outdated browser version, a corrupted browser cache, DNS configuration issues, and an overly strict firewall.

ERR_CONNECTION_TIMED_OUT Fix

1. Check your internet connection: This is the quickest fix. Double-check that your internet is working properly. If it isn’t, restart your router or modem.
2. Update your browser and clear the cache: Make sure you have the latest version of your browser and clear the cache to remove outdated files that could cause the error.
3. Flush your DNS cache: The steps to flush your DNS cache vary depending on your operating system. Refer to this article on How to Flush DNS Cache on Windows, MacOS, and Linux for a detailed guide.
4. Disable firewall: Temporarily turn off your firewall and antivirus software to see if they are blocking the page from loading. Remember to turn them back on afterward to stay protected.

6. Parse Error (Syntax Error)

WordPress runs on PHP; therefore, it relies on well-structured, error-free code to function correctly. If there is even the tiniest error in your PHP code, such as a missing bracket or a deleted character, your entire site will break, and that’s when the “Parse Error: Syntax Error, Unexpected” message is displayed. This error can be caused by corrupted core, theme, or plugin files, as well as incompatible custom code.

Parse Error Fix

1. Restore a recent site backup: If you have a recent backup of your site before the Parse Error occurred, you can revert to that version using the backup feature in your hosting dashboard. You can also manually restore your site backup via FTP. 
2. Disable recently added plugins or themes: Newly added plugins or themes with coding issues could cause the Parse Error. Disable them via FTP by navigating to /public_html/wp-content/plugins/ or /public_html/wp-content/themes/ and renaming them to see if the error resolves. 
3. Replace broken WordPress files: Follow the steps in this section to replace any broken core WordPress files. 
4. Add custom code with a code snippet plugin: If you added custom code to your site’s theme or plugin files, delete it via FTP and then re-add using a code snippet plugin like WPCodeBox that can identify common syntax errors before your code goes live. If you’re still having trouble identifying the syntax error, enabling debug mode with WP Debug Toolkit will show you the exact file and line number where the error occurred, making it much easier to fix.

7. Fatal Error: Allowed Memory Size Exhausted 

Similar to the “ERR_CONNECTION_TIMED_OUT” error, if you’re on a shared hosting plan, you may encounter the “Fatal Error: Allowed Memory Size Exhausted” error.

This happens because the PHP memory limit is usually capped on shared hosting plans. As a result, if you try to perform processes that require more PHP memory than what’s allocated—such as uploading large media files or installing resource-intensive plugins and themes—it triggers the “Fatal Error: Allowed Memory Size Exhausted” message.

However, keep in mind that you might not see this message directly on the webpage if you’re using a newer version of WordPress. Instead, you’ll see the generic “There has been a critical error on this website. Please check your site admin email inbox for instructions.” message.

Allowed Memory Size Exhausted Fix

1. Increase PHP memory limit: Add the code define('WP_MEMORY_LIMIT', '512M'); to your wp-config.php file to raise your site’s PHP memory limit. You can also adjust the PHP memory limit via your .htaccess and php.ini files. If you’re not sure whether a plugin is causing the memory exhaustion, WP Debug Toolkit can help identify resource-heavy processes that might be consuming too much memory.
2. Disable unused plugins: Having too many plugins on your site can use up excessive PHP memory, so it’s important to disable any plugins that aren’t actively serving a purpose.
3. Upgrade your hosting plan: If all other solutions fail, it might be time to upgrade your hosting plan to one with more resources to ensure your site runs smoothly.

8. “Briefly Unavailable for Scheduled Maintenance” Error

The “Briefly unavailable for scheduled maintenance. Check back in a minute” message isn’t an error on its own. It usually appears when WordPress puts your site in maintenance mode during updates to core files, plugins, or themes.

However, sometimes your site gets stuck in maintenance mode even after updates are finished, which can be a problem because it prevents you and your visitors from accessing the website.

Two main reasons this error might happen are: updates being interrupted halfway due to memory issues or server timeouts, and trying to update too many plugins and themes at once.

“Briefly Unavailable for Scheduled Maintenance” Fix

1. Manually delete the .maintenance file: The .maintenance file is created when maintenance mode is activated and is automatically removed after it’s deactivated. However, if your site is stuck in maintenance mode, you need to access your /public_html/ folder and locate the .maintenance file to delete it manually. This will fix the issue.

9. ERR_TOO_MANY_REDIRECTS Error

When your website gets stuck in an infinite redirect loop, it displays the ERR_TOO_MANY_REDIRECTS error message. This issue is usually caused by misconfigured settings on your website, such as incorrect WordPress, server, or HTTP settings. 

Browser caching problems, plugin conflicts, and issues with third-party services can also be responsible for this error.

ERR_TOO_MANY_REDIRECTS Fix

1. Clear cookies and cache for your site: In your browser settings, find your website and select the option to clear its cookies and cache.
2. Check HTTP settings: Confirm in your hosting dashboard that you have a valid SSL certificate installed and that HTTPS is enforced properly. Only enable HTTPS after installing a valid SSL certificate.

3. Regenerate the .htaccess file: If your site’s redirect rules are misconfigured in the .htaccess file, it can cause redirect loops. Follow the steps outlined here to regenerate the file.
4. Clear server-level and CDN cache: Clear your server cache through your hosting dashboard, and clear your CDN cache from your CDN provider’s dashboard.
5. Contact Hosting Provider: If you’ve tried all the fixes and still face issues, contact your hosting provider’s customer support for assistance.

10. HTTP Image Upload Error

The HTTP Image Upload Error occurs when you try to upload an image to your website, but the server encounters issues processing your request. This could be due to various reasons, such as low memory, plugin conflicts, large image size, server glitches, or timeouts. 

HTTP Image Upload Error Fix

1. Retry the image upload: If the error occurred due to a temporary server glitch, then retrying the upload is all you need to fix it. 
2. Clear website cache: Use the caching plugin installed on your site to delete outdated data that might be causing the error. 
3. Increase PHP memory limit: Edit the PHP memory limit value in the wp-config.php file or ask your hosting provider for help. 
4. Set GD Library as the default image editor: WordPress’s Imagick image editor uses a lot of memory, which can cause the HTTP error. Consider switching to the GD Library image editor, which is more resource-efficient. To do this, install a code snippet plugin like WPCodeBox and add the following code to your site:

add_filter( 'wp_image_editors', function( $editors ) {
return array( 'WP_Image_Editor_GD', 'WP_Image_Editor_Imagick' );
});

5. Deactivate image optimization plugins: Some image optimization plugins might cause issues when uploading images. If you use any of them, deactivate them to see if that resolves the error. 

11. WordPress Not Sending Emails Error

WordPress not sending emails is a common problem faced by many users who rely on the WordPress email system to send automated, action-triggered messages to site visitors. 

It could be that the emails never arrive or end up in the recipient’s spam folder. The main reason for this issue is that the email setup is incorrect. 

WordPress Not Sending Emails Error Fix

1. Double-check email settings: Go to Settings › General and verify the Administration Email Address field to make sure the correct email address is entered.

2. Check server configuration: WordPress uses the mail() function in PHP to send emails, so confirm with your hosting provider that this function is enabled on your server.
3. Implement SMTP for emails: SMTP allows you to use a dedicated email server, which is more reliable than the mail() built-in function. Set it up with an SMTP email plugin like FluentSMTP.
4. Check your plugins: Security or spam prevention plugins might interfere with email delivery if they are not correctly configured. Temporarily disable them to see if the issue is resolved. 

12. Locked Out of WordPress Admin

Nothing is more frustrating than being locked out of your WordPress site’s admin area. It means you can’t make any changes until you find a way to fix the problem.

You can be locked out for several reasons, including entering incorrect login credentials, losing admin privileges, or trying to log in too many times. You can also get locked out due to common WordPress errors like the Parse Error, White Screen of Death, and Database Connection Error.

Locked Out of WordPress Admin Fix

1. Double-check your login credentials: A small mistake in your login details could prevent you from accessing your account. Verify that you are entering the correct credentials.
2. Reset your credentials from cPanel: You can change your password using phpMyAdmin in your cPanel. For detailed instructions, see the Reset Your Password WordPress documentation.
3. Create a new admin user: You can also add a new admin account to your WordPress site using phpMyAdmin in your cPanel. For guidance on this process, refer to the article Add WordPress Admin User with phpMyAdmin.
4. Temporarily deactivate your security plugin: If a security plugin that limits login attempts is active, you may get locked out of your WordPress admin. Using your hosting provider’s file manager or FTP, go to /wp-content/plugins/ and rename the security plugin folder to deactivate it. If that’s the cause of the issue, it should be resolved, and you can then log back in to your admin dashboard easily.

13. “Maximum Execution Time Exceeded” Error

If you see the “Fatal Error: max_execution_time exceeded” message on your website, it means that a PHP script in WordPress is taking longer to run than the server’s time limit allows. 

Limits are set on the server to keep processes efficient and ensure everything runs smoothly on your site. If any process exceeds the allotted time, the server times out, and that’s when the “Fatal Error: max_execution_time exceeded” message appears.

Maximum Execution Time Exceeded Error Fix

1. Increase max_execution_time: You can increase WordPress’s max_execution_time using three primary methods: through .htaccess, php.ini, or wp-config.php. The steps to do this are outlined here. 
2. Install a plugin to adjust the maximum execution time automatically: Plugins like MaxUploader simplify the process of changing the maximum execution time without requiring code. 
3. Contact your hosting provider: If the other solutions don’t work, contact your hosting service provider for assistance in fixing the error.

14. 403 Forbidden Error

The 403 Forbidden Error occurs when the server cannot grant access to a specific page due to restricted permissions. You might see this error during a WordPress installation, when visiting a page on your site, or when trying to access the wp-admin login page.

Common causes of the 403 Forbidden Error include misconfigured file permissions, firewall restrictions, entering an incorrect URL, conflicting plugins, missing index page, server security settings, and a corrupted .htaccess file, among others.

403 Forbidden Error Fix

1. Check the URL and reload the page: Make sure you entered the correct URL, and refresh the page if it’s just a temporary glitch.
2. Clear your browser cache and cookies: Do this to remove any outdated cache or cookie data that might be causing the error.
3. Check file and directory permissions: Your file permissions should be set to 644, while directory permissions should be 755. Verify that they are correctly set in your File Manager via cPanel or FTP. If not, update them.

4. Regenerate the .htaccess file: The steps are outlined here.
5. Disable all plugins: If conflicting plugins are causing the error, disabling all plugins should fix the issue. Access your File Manager via cPanel or FTP, then navigate to the /wp-content/ folder and open the plugins folder. Rename it to disable all plugins. Then, re-enable them one by one from your admin dashboard to find the problematic plugin.
6. Contact your hosting provider: If the above fixes do not resolve the issue, your hosting provider can assist you with troubleshooting further.

15. 503 Service Unavailable Error

The 503 Service Unavailable Error appears on your webpage when the server is too busy to process your request. This often happens due to scheduled maintenance or a temporary overload. 

However, there are cases where plugin conflicts, resource-intensive themes, or server misconfigurations may cause it. The best way to fix the 503 Service Unavailable Error is to follow a systematic approach.

503 Service Unavailable Error Fix

1. Refresh the page: Your ‘504 Service Unavailable’ Error might be caused by a temporary server overload. First, try refreshing the page to see if that fixes the issue.
2. Check your server status: Confirm through your hosting provider dashboard that your site’s server is not currently in maintenance mode. If it is, wait a while before trying to load the web page again.
3. Check your firewall settings: Make sure your firewall isn’t blocking harmless traffic to the server.
4. Limit the WordPress “Heartbeat” API: The WordPress “Heartbeat” API can consume excessive resources, which may cause a 503 error. Limit its activity via your caching plugin or custom code.
5. Deactivate all plugins: Deactivate all plugins to see if the 503 error is caused by plugin conflicts. You can complete this task through FTP or cPanel by following the steps outlined here.
6. Switch to the default WordPress theme: Deactivate your current theme via FTP or cPanel, and switch to WordPress’s default theme to check if the error is related to your theme.
7. Review server resource usage: Monitor your server’s resource use from your hosting dashboard, and consider upgrading to a higher plan if you’re exceeding your limits.

16. 504 Gateway Timeout Error

Sometimes, the servers that need to communicate to fulfill a web page request (the proxy and upstream servers) run into glitches that affect their ability to do so on time, leading to a 504 Gateway Timeout Error. 

The error is usually temporary, and there are several reasons why it may occur. Some of the reasons include network congestion issues, the server undergoing maintenance, high traffic volume, firewall interference, and resource limitation issues with the hosting provider.

504 Gateway Timeout Error Fix

1. Reload the web page: A simple page reload might fix the 504 Gateway Timeout Error.
2. Check your server logs: Use a WordPress debugging plugin to enable debug mode on your site and view your error logs, which will include details about issues affecting your server. This can help you identify the cause of the error.
3. Check for DDoS attacks or spam/bots: If your site is being spammed by bots or attacked, it can slow down your server and cause a 504 error. Use your hosting dashboard or website analytics tools to monitor your traffic for any unusual activity.
4. Deactivate your WordPress firewall: An overly strict firewall may incorrectly block requests. Temporarily disable it to see if the error goes away.
5. Check for server issues with your hosting provider: If you’re on a shared hosting plan, the 504 error might not be directly caused by your site. It could be due to a high-traffic site on the same server. Contact your hosting provider to determine if this is the case.

17. Plugin or Theme Conflicts

Plugin and theme conflicts are among the most common errors faced by WordPress site administrators. It occurs because these software programs often try to modify the same website feature, are coded in ways that don’t follow industry best practices, or become outdated and incompatible with your current WordPress installation.

Sometimes, it may also be your own custom code, added to change specific WordPress features, that causes the conflict.

When you experience random display issues, site crashes, missing functionality, or slow performance, there’s a high likelihood that it is caused by plugin or theme conflicts.

Plugin and Theme Conflicts Fix

1. Clear your browser and site cache to ensure you’re not viewing an outdated version of your site. 
2. Keep your WordPress core, plugins, and themes updated as new versions are released. 
3. Test for plugin conflicts by deactivating all plugins, then reactivating them one at a time to identify conflicts and consider alternatives. 
4. Check for plugin versus theme conflicts by switching to the default WordPress theme to see if the issue resolves; if it does, your theme may be causing the problem, and you can look for a more compatible theme.

18. WordPress Loading Slow

A slow-loading WordPress site can be frustrating and may even cost you valuable business, ultimately harming your reputation. 

There are several reasons why your site may suddenly start to load slowly. Some common causes include running an outdated version of WordPress, using too many plugins, having bulky themes, uploading large images, failing to use a Content Delivery Network (CDN) or caching, unoptimized CSS and JavaScript, and hidden malware.

WordPress Loading Slow Fix

1. Update your WordPress installation, plugins, and themes: Keep your WordPress installation, including plugins and themes, updated to benefit from performance improvements that can boost your site’s speed. 
2. Disable any unnecessary plugins: If you have plugins you don’t actively use, disable them, as they can consume resources and slow down your site. 
3. Use a good caching plugin: Caching tools like WP Rocket enhance your site’s speed by generating static versions of pages that load more quickly. 
4. Optimize images on your website: Compress images before uploading, or use an image compression plugin like ShortPixel to compress them automatically. 
5. Use a CDN: A CDN delivers your site’s content through a global network of servers, serving visitors from the closest server to reduce page load times. 
6. Use a trusted hosting service provider: If your hosting service doesn’t provide enough resources, it could negatively affect your site. Consider using a hosting provider that is specifically optimized for WordPress sites.

19. Destination Folder Already Exists

When you add a theme or plugin to your site, a folder is created in your file directory. However, sometimes the installation process may fail midway through for various reasons, leaving an empty folder for the theme or plugin. 

If this happens and you try to add the theme or plugin again, you will likely see the “Installation Failed: Destination Folder Already Exists” error message.

Destination Folder Already Exists Fix

1. Overwrite the old plugin or theme folder: When you see the “Destination Folder Already Exists” message while uploading a plugin or theme, click the “Replace Current with Uploaded” button on the upload page to overwrite the existing folder. 
2. Delete the existing folder: You can also manually delete a plugin or theme folder via FTP or the File Manager provided by your hosting provider. Navigate to /wp-content/plugins/ if it’s a plugin issue or /wp-content/themes/ for a theme issue, then delete the folder of the plugin or theme you’re trying to install.

20. DNS_PROBE_FINISHED_NXDOMAIN Error

When your domain name cannot find the IP address of your website to establish a connection, you encounter the DNS_PROBE_FINISHED_NXDOMAIN error message. 

The message appears differently depending on the web browser you are using. For instance, if you use Google Chrome, the message will say “This site can’t be reached”.

The main causes of this error include network connectivity problems, domain name misconfiguration or expiration, a corrupted DNS cache, and interference from VPNs or antivirus software.

DNS_PROBE_FINISHED_NXDOMAIN Error Fix

1. Refresh your internet connection: Disconnect and reconnect your modem or router to reset your internet if it’s causing the error.
2. Flush DNS cache: This clears any outdated IP addresses that may be triggering the DNS_PROBE_FINISHED_NXDOMAIN error.
3. Check your domain name setup: Verify your DNS settings to ensure your domain points to the correct nameservers. You can usually find the correct nameserver info in your hosting dashboard.
4. Temporarily disable your VPN and antivirus: Your VPN or antivirus may accidentally block access to your website, so temporarily disabling them might resolve the error.

Common WordPress Errors — Frequently Asked Questions

Common WordPress Errors — Related Information

• Best Plugins for WordPress Debugging and Troubleshooting
• How to Find and View WordPress Error Logs