Sometimes you may encounter a HTTP error like HTTP 404 error and HTTP 403 Forbidden Error when visiting a site. The HTTP 500 Internal Server Error is also a general HTTP status code indicating the website cannot display the page properly. It means something is wrong on the server, but the server cannot make sure the problem.
There are several causes may result in this error and it’s not easy to judge the reasons and find a corresponding solution. In order to help readers solve this problem easily, we today come out this tutorial to introduce the reasons and solutions in detail. By finding the cause of the error, you can quickly and correctly remedy this problem.
What Causes HTTP 500 Internal Server Error?
HTTP 500 Error can present on any browser, any operating system, and any websites, not only WordPress sites. It occurs when no more specific message is suitable, such as the following.
As every website is allowed to customize error message, you may see it in many ways, such as 500 Internal Server Error, HTTP 500 – Internal Server Error, Temporary Error (500), etc.
No matter what way it showcases, the cause is the same, for the PHP memory limit, plugin conflicts, corrupted .htaccess file, and more. Because of the general essence, it doesn’t clearly showcase any reasons, but we can common judge its causes as the following:
- Unexpected errors in both WordPress core and plugins.
- Bugs in WordPress plugins and themes.
- PHP memory limit is insufficient.
- Bugs in web server software, such as Apache, PHP, etc.
- Incorrect web server configuration file.
- And more.
In the below content, we guide you to fix the 500 error for these possible reasons.
How to Fix the HTTP 500 Internal Server Error?
# Checking The .htaccess File
Corrupted .htaccess file is the most likely cause of HTTP 500 Error. To remedy the error, you can first check the file by renaming .htaccess file to a new name. You can find the file by logging into your server control panel or through FTP client. Personally, we complete the whole process in cPanel.
Log into cPanel and click on the File Manager icon in the Files section. Select the box of document Root and choose the domain you need to access from the drop-down menu. Then, select the checkbox for Show Hidden Files(dotfiles) and click Go button to the next step.
Find .htaccess file in the directory where you can find wp-content, wp-includes and wp-admin folders. Once located it, right click on the file and then you will see a list of options, choose Rename and it will present you a new tab to type a new name.
After renamed the file, try to refresh the site to check whether the 500 Error is solved. If it did, you successfully fix the error and you can go to WordPress Dashboard -> Settings -> Permalinks and click the Save button. By this way, WordPress generates you a new .htaccess file with proper rewrite rules.
If the 500 Error is still not resolved, you should continue for the next steps.
# Increase PHP Memory Limit
The HTTP 500 Error sometimes happens due to the lower memory limit. To fix this problem, you can modify the memory_limit line in the php.ini file with the below tips:
- Create a new text file named as php.ini
- Copy and paste the below code into it
memory_limit = 256M
- Save the file and upload it under /wp-admin/ folder
Then, check for your site. if the error is solved, you temporarily succeed but the thing is still not complete. You should also contact for the WordPress hosting provider to access the server logs for finding the certain cause.
If the HTTP 500 Error is still unresolved by increasing memory, you may need to do tedious trouble shootings.
# Disable All Plugins
If you haven’t fixed the error with the previous methods, you need to consider the plugin errors. The conflicts between plugins and the incompatibility with WordPress are both possible to cause 500 Error. Unfortunately, it’s unable to find the cause with easy method.
You need to disable all plugins of your site at once. If the error is successfully fixed, you can make sure that one or some specific plugins results in this error. So you can reactivate plugins one after the another until finding the one caused this issue. Then, delete it and feed issue to the developer.
Seriously, you may be unable to solve the error by disabling all plugins. In this condition, you can re-upload the WordPress core files or just contact the web host for helps.