Internal Server Error “Error 500”, is one of the most common WordPress errors you will often find. The error is not just specific to WordPress. We cannot find the exact issue from this error. There can be various causes for an Internal Server Error.
The most common reason for a WordPress Internal Server error is a plugin or a theme functionality. The internal server error in WordPress can also be caused due to a corrupted .htaccess file or a PHP memory limit. Sometimes the Internal Server Error may be found only in the WordPress Admin panel.
Let us check how to deal with the Internal Server Error for WordPress in detail:
Fix Corrupted .htaccess file
First rename the .htacess file as .htaccess_bak and try reloading the website. If the site is loading fine now, then it means that the issue was with the corrupted .htaccess. .htaccess file can be found in the same directory where the WordPress is installed.
Once this done, make sure that you go to the admin panel, go to settings >> Permalinks and then click on the “Save” button. Saving Permalinks will generate a new .htaccess file for the proper functioning of your WordPress website. This is to make sure proper rewrite rules for your website. This ensures that the site will not return a “404 file not found ” error.
Increase the PHP memory limit
If the .htaccess trick did not fix your error, go on to the next step. The internal server error can also occur due to the exhaustion of PHP memory limit. You can contact your host and ask them to increase the PHP memory limit to help you. You can also do it yourself. I will guide you to do the steps for the same in a tutorial. If the Internal server error is only in you WordPress admin panel, or anytime you try to upload pictures to the admin panel or when you try to log in, please follow the below steps:
- Create a text file and name it as php.ini
- Paste this code in there: memory=64MB
- Save the file Upload the file to your /wp-admin/ folder using FTP.
After doing this you need to consult your web-hosting company for the error logs to find the proper reason for the error and to suggest a fix to avoid this issue again. Usually, the error comes with an improperly coded plugin or theme.
Deactivating all Plugins
If the above solution also couldn’t help you, here is the next step, Deactivating plugins. You need to deactivate all the plugin first to have a look whether the site loads now. I will teach on how to deactivate the plugins without wp-admin in a tutorial.
If this could fix your error, then the issue is with a plugin installed. Go and reactivate each plugin, one by one (one at a time) and find out which caused the issue. Disable the plugin that caused the error and report it to the plugin author or support.
Re-upload the Core Files
If the plugin trial also couldn’t fix your issue, then the next step is to re-upload wp-admin and wp-includes folder from fresh WordPress install package.
Don’t worry, this won’t remove any of your information. This can solve your issue in the case of any corrupted file.
If none of the above fixes couldn’t resolve your issue, then the last solution is to consult your hosting provider. They can find a reason for the error from the server logs.
Please let me know in comments below if any of the fixes resolved your error. Also please help me improve the article by giving your valuable feedback in comments. If you were able to fix the Internal Server with some other solution which is not mentioned above, please update that too.
Thank you for reading 🙂