How to Solve 500 Internal Server Error in WordPress?
If you’re surfing the web atleast for a year now, you might’ve noticed the HTTP 500 Internal Server Error on some blogs. This HTTP 500 error is the most common WordPress error that leaves the WordPress beginner in panic. In case you’ve encountered this Internal Server Error on your WordPress blog, just don’t panic. You can easily fix this issue by following the steps below.
What causes Internal Server Error in WordPress?
How to Fix the Internal Server Error in WordPress?
1.Check for Corrupt .htaccess File
One of the few causes for getting Internal server error is the corrupted .htaccess file. In order to check it, simply use your FTP software and rename your main .htaccess file to something like .htaccess_old. You can locate the file in the same location where the wp-content, wp-admin folders are located. Once renamed, try to load your blog and if it loads well, then there is a problem with your .htaccess file.
Note: If the file is corrupted, you’ll need to regenerate the .htaccess file again or else your posts will return a 404 error. To do so, go to WordPress dashboard > Settings > Permalinks and simply click ‘Save settings’. It will then generate a new .htaccess file with correct rewrite rules.
In case your blog didn’t load even when you rename your htaccess file, then it means there is no problem with your file. You may now rename the .htaccess_old back to its original name and move on to the next step.
2.Increase the PHP Memory Limit
If the internal server error only appearing when you either try to login to your blog or while uploading an image, then the problem is with the memory limit. In order to increase the PHP memory limit, simply follow the steps below.
- Open notepad and paste the following code in it.
- Save the file with the name ‘php.ini’
- Upload it into your /wp-admin/ folder either directly using the File Manager (cPanel) or using any FTP software like FileZilla.
The memory limit problem will be solved temporarily but not permanently. It is because, the problem may rise again if you’re using a plugin or theme that is poorely coded. So, it is better to contact your WordPress hosting provider for the exact diagnostics.
Even after trying the above fix, the internal server error may still exist sometimes, which means your WordPress blog need to be checked in-depth.
There are two ways to hard-core trouble shoot your WordPress blog for errors.
- Deactivate All Plugins
- Re-upload Core WordPress Files
3.Deactivating all WordPress Plugins
If none of the above fixes didn’t solve your problem, then the internal server error may be caused by some poorely coed plugin. Unfortunately, there is no proper to judge which particular plugin is causing the problem.
How to Deactivate All PLugins when not able to Access WP-Admin?
Use any FTP software or your default File Manager (from cPanel) and go to /wp-content/ folder. In that you’ll find a folder called ‘plugins’. Renaming the folder will automatically deactivate all your plugins. Once done, you’ll be able to access your WordPress admin panel (login).
Now, try to activate one plugin (Plugins) at a time until your site breaks again. You can then know which plugin is causing the problem and get rid of it, report the error to the author of the plugin.
4.Re-upload Core Files
In case the above plugin option didn’t work too, then the final solution would be to re-upload the wp-admin and wp-includes folder from a fresh WordPress build. Don’t worry! This will not remove any of the existing information from your blog but could solve the internal server problem in case any of these files were corrupted.
There is also a worst scenario where none of the above solutions work. In such situations, you should contact your hosting provider and seek help.
Did you encounter the Internal Server Error in your WordPress blog earlier? What solved your problem? Please do share with us.
Incoming search terms:
- bluehost http error 500
Share This Article
Get Free Email Alerts
And, Next Confirm Your Email Subcription