Over the past few days, some of our users have reported that they have encountered an error on the WordPress 500 homepage. Common Solutions to Internal Server 500 Error The two most common causes of this error are corruption. htaccess and your server’s PHP memory limit has been exceeded. … The htaccess file in your WordPress directory can get corrupted after installing a plugin or making any other changes to your WordPress site. March 29, 2016
- Colin Newcomer
We’ve all been to this: a site that was working fine a few seconds ago suddenly decides to start a capture and throws an internal server error. If you’re lucky, the WordPress admin area will still work, but in some cases it may not work. In this article, we will explain what an internal server error is and, more importantly, how to fix it.
Important! Always make a full backup of your site (even if it’s not working properly) before making any changes – better safe than sorry!
Let’s get started.
What Is An Internal Server Error?
Internal server errors annoy both users and developers, because they don’t provide any information about the cause of the problem – they just tell you. Imagine going to the doctor and saying, If it hurts you, but refuse to reveal where the pain was – it will be very difficult for the doctor to cure it! This is an internal server failure issue – there is no indication of where the problem is.
(click to enlarge)
Also, the title “Internal Server Error” can be misleading, since in almost all cases your host (and / or server) is not at fault. If you look at the HTTP specs, you can see that an internal server error means:
The server encountered an unexpected condition that prevented execution of the request.
The server itself is fine – it just stumbled upon something that it cannot understand.
To figure out what’s going on, you need to troubleshoot a bit, and try andmistakes. By systematically examining what might go wrong, you can figure out what is causing the problem and, more importantly, how to fix it.
How To Fix Internal WordPress Server Error 500
We recommend that you follow these steps in order. So, start at step 1 and go through the list. In some situations, we recommend following any of these steps depending on the results. But in general, you go out!
Also, remember that we always recommend that you back up your site before making any changes to this list. If you can’t access your WordPress dashboard to use the backup plugin, you can still back up from your hosting dashboard. Contact your host’s support team for assistance if you are unsure how to do this.
Now let’s move on to the repair …
0. Enable Debugging
The first step is to at least try to figure out the error – you might be lucky! Depending on how your server handles errors, what you see may not be error at allflexible server. Instead, it could be a bug in your site code (usually plugin or theme code).
To check if this is the case, edit the
wp-config.php file in the root of your website:
- Upload the file (via FTP).
- Open it (in a text editor).
- Search for
If the string already exists, replace
true and upload the file to the server again.
If this line is not in your config file, create it by adding the following line of code anywhere above the line that says
/ *. Done, edit! Have fun blogging. * / :
define ("WP_DEBUG", true);
Reload the site and see if the error changes. If so, and you now see a Fatal Error message for a specific line of code in a specific file, then this is a relatively simple code error. Assuming the error is related to a plugin or theme, you should disable that product and / or fix the problem yourself (or have someone check it out if you can’t figure it out) that(occurs).
Note. After completing this step, you should change the value of
false to avoid accidentally exiting debug mode. By default, debug messages are displayed throughout the site, confusing visitors and posing a potential security risk.
1. Make Sure Your WordPress Dashboard Is Running
In the next step, check if you have access to your WordPress backend dashboard.
Contact your website administrator at
http://yoursite.com/wp-admin/ . If this page loads correctly and you can log in, you can be sure that the problem is with the plugin or your theme. If your administrator is booting, skip to step 2. Otherwise, skip to step 4.
2. Disable All Plugins
Now it’s time to check if the problem is with the plugin. It is not possible for a plugin to cause any problems if disabled. The easiest way to test this is to disable all plugins at the same time. This will not delete your plugins and you will not lose your data (which is still overare stored in your database). This will disable code execution, which will fix the problem where the plugin code throws an internal server error.
If your WordPress dashboard is working correctly, you can disable plugins as follows:
- Go to the Plugins section of your WordPress dashboard.
- Check the box to select all plugins.
- Use the bulk action dropdown to disable it.
- Click Apply.
If for some reason you cannot deactivate plugins from the control panel, you can also deactivate them via FTP by following the instructions below:
- Connect to your WordPress site server via FTP.
- Go to the
- Rename the
If you’ve disabled all plugins, but your site still won’t load, go to step 3.
After your site is up and running, the next step is to determine which plugin is causing the problem.
To do this, you need to re-activate the plugins individually. After activating each plugin, keep looking for this internal server error. Once you find the culprit, it’s up to you to decide what to do with it. It is best to leave the plugin disabled and notify the author immediately.