How to Fix the 500 Internal Server Error in WordPress
How to fix the 500 internal server error in WordPress is one of the foremost common WordPress errors. Since the error doesn’t give the any other information, many beginners find it quite frustrating.
WordPress is the best CMS. In this article, I’ll attempt to make sense of this internal server error in WordPress and will shows you the method to solve this error.
What is the 500 internal server error?
The web definitions of the 500 internal server error are not so clear. There’s no accurate indication on what really went wrong and caused this error.
The only thing that is true is that the cause of this error is some operation that went wrong on the website’s end. Particularly in WordPress’s case, this will a script that’s a part of a topic or a plugin did something it shouldn’t have done, and now your server has crashed and caused error. According to expert other possible causes of internal server error in WordPress is corrupted .htaccess file and PHP memory limit.
How to resolve 500 internal server error
Most of the time, you can solve the 500 internal server error using 6 steps:
Table Of Content
1. Turn On Debug Mode
Whenever you face 500 internal server error, I will like to recommend turn on the debug mode. While this might not fix the matter, it’s going to offer you more insight into what’s happening with your website.
You can turn on debug mode by editing your site’s wp-config.php file. Once you’ve accessed this file, look for WP_DEBUG in that file. If you discover, you ready to set it “true”. If you don’t see it in that file, you’ll need to create it yourself. At the end you have a line that appears like this:
define( "WP_DEBUG", true );
After saving the changes, reload your site to ascertain if anything has changed. If you’re lucky, the server error may disappear or replace by particular error, that one really tells you where the problem is.
If this is often the case, take a glance at where is the error. If it’s within a plugin folder, disable that plugin, the error should get away.
Even if turning on debugging doesn’t offer you an excellent result, until the resolve does not resolve, it’s a simple idea to go away it turned on. It’ll offer you and any developers more insight into what’s happening. After done with the maintenance Don’t forget to turn off the debug mode once everything is fine.
2. Deactivate All Plugins Or Switch Theme
If you’ve access to your dashboard, you should deactivate all of your plugins. Look if website loads without the server error the difficulty was with one of your plugins. You can switch them on one-by-one to work out which one caused the problems.
You can also switch your theme to a default, unaltered WordPress theme like Twenty Fifteen or Twenty Sixteen. If the location loads without the internal server error, the difficulty was within your theme.
We’ve noticed that quite few of those errors are literally caused by plugins, so this may be the solution of your problem.
3. Check .htaccess File
The .htaccess file, if it exists, contains number of rules that tell the server that what to do in certain circumstances. It’s commonly used for rewriting URLs or preventing access to your site for malicious intent.
Use FTP editor and check if you’ve an .htaccess in your WordPress root folder. You also have to check your FTP hidden file list.
If you find an .htaccess file there, make a backup of the file then delete all the contents within that file, or the entire file. This might remove some important rules, but if the internal server error was caused by an error within the file, this may tell you.
If the error is now resolved, the difficulty was with the .htaccess file. Try restoring the file then deleting blocks of it. If at some point the location starts working, you recognize that which block the creating the problem. You can short it to one line like usually. You can then remove that line or ask your developer or your host for further assistance.
4. Increase Memory Limit
We’ve never personally run into this issue, but we’ve heard that increasing your memory limit may help. We assume that this is often more of a problem in shared environments. To do this, open your wp-config.php enter the WordPress root directory and look for WP_MEMORY_LIMIT. If it exists, change the worth to something like “64M”. If it doesn’t, paste the subsequent line into the file:
If this works then you’ve only solved the problem temporarily. Likelihood is that you simply have a faulty little bit of code somewhere (which might be a 3rd party plugin) that’s exhausting your resources. If your host has monitoring available, take a glance at your resource usage with various plugins on/off to get a far better idea of what’s wasting those precious megabytes.
5. Ask To Your Host
There are a couple of uncommon issues which may cause internal server errors in WordPress, but at now it’s going to be best to ask your host. The difficulty might be a real server issue, which they will at least confirm an issue and that they also can check out things like file permissions and other sources.
Or, you would possibly just want to modify to a far better host that has servers that are more optimized to run WordPress sites. This not so expensive. There are hosts that offer you the best WordPress experience for as little as $0.8 a month.
6. Reinstall Or Update WordPress
Last possible solution of this problem is reinstallation of WordPress or update the WordPress to latest version. To fix this issue reinstall the WordPress. Furthermore it will also fix the file permission problem.
To do this we will recommend you to follow the manual WordPress update instruction or complete guide to install WordPress.
Internal server errors in WordPress are usually not caused by actual server faults. Most of the time, they will be corrected relatively easily using the methods described above. If you have any confusion, always ask your host, they need much more sophisticated tools than you are doing to locate and fix issues.
I always recommend switching on debug mode while you’re working things out and ruling out plugin and theme issues since this is often what any support technician would ask you to do first, or they might do themselves.
If you are still unable to resolve the issue then contact WordPress Expert to resolve this error.