How to Fix the Internal Server Error in WordPress
The 500 Internal Server error is not always due to WordPress. It can be caused by other issues on the server as well. This article addresses the common causes of WordPress's 500 Internal Server errors.
Corrupted .htaccess File
To address the issue with a corrupted .htaccess file, you can try creating a new .htaccess file. Here are the instructions on how to address this issue.
- Log in to cPanel.
- Look for the Files section, and click on the File Manager icon.
- Click on the Settings box on the upper-right side.
- Check the box for Document Root and select the domain name you wish to access from the drop down menu.
- Make sure Show Hidden Files (dotfiles) is checked.
- Click Save. The File Manager will open in a new tab or window.
- Look for the .htaccess file in the list of files. You may need to scroll to find it.
- Right-click on the .htaccess file, then select Rename. Rename the file as .htaccess.bak. Alternatively, you can click on the icon for the .htaccess file, then click on the Rename icon at the top of the page.
From the left-hand navigation menu of the WordPress Dashboard:
- Navigate to Settings, then click on Permalinks.
- Review the settings to be sure they are set up properly.
- Click the Save Settings button.
- Try reloading the site to see if the 500 Internal Server error has been resolved.
Still, Getting a 500 Internal Server Error?
Increase PHP Memory Limit
If the error persists, try Increasing the PHP memory limit. Please refer to this article for more information on resolving the PHP Memory Limit Error.
Deactivate/Reactivate All Plugins
If increasing the PHP memory limit does not resolve the 500 Internal Server error, it may be caused by one or more plugins installed on WordPress. Oftentimes, if a new theme is installed, a previously installed plugin will not be compatible, resulting in the 500 Internal Server error.
- Log into cPanel.
- In the Files section, click on the File Manager icon.
- Select the Web Root (public_html/www), and the Document Root for the domain using the WordPress install, then click save.
Click to expand the public_html folder, then navigate to the /wp-content folder.
- Right-click on the /wp-content/plugins folder, then rename it as plugins.old. This will most likely deactivate all plugins and lock the WordPress admin area. You can still perform these steps from within the File Manager.
- Reactivate the plugins folder by following the above instructions and renaming the folder back to plugins. This will allow you to reactivate each plugin individually to isolate the offending plugin and resolve the 500 Internal Server Error. This should also allow access to the WordPress Dashboard again.
From the WordPress Dashboard:
- Reactivate each plugin (one at a time) and refresh the website to see if the issue has been resolved.
The 500 Internal Server error is not always due to WordPress. It can be caused by other issues on the server as well. This article addresses the common causes of WordPress's 500 Internal Server errors.Before making any of the following changes to your website, it is suggested that you backup your website so that you can revert to a previous version if something goes wrong.