WordPress Tutorials

5 Ways to Fix Internal Server Error in WordPress

Unquestionably, webmasters may encounter some errors when they surf the Internet. But most of them do not know how to deal with the issues quickly and correctly by themselves, especially for new beginners.

There is no doubt that there are many errors webmasters may suffer from and in below article, we will focus on one of the most common issues, internal server error, trying to help webmasters handle this issue easily.

What Is Internal Server Error

We believe that internal server error is not new for the majority of webmasters. It is an error that generated by your web servers. As long as webmasters encounter this error, they can clearly know something wrong, but they cannot tell the specific information of the error condition because this error is not specific to WordPress.

There are some reasons can explain the error, such as PHP memory limit, corrupted .htaccess file and others, but webmasters need to check them one by one. So please read the following article if you are eager to get this error resolved.

Corrupted .Htaccess Files Checking

The first step that webmasters need to do is to check the corrupted .htaccess files if you want to fix the internal server error in WordPress. To check the .htaccess file, you can rename the main .htaccess to a new one. After that, you should use the FTP to login to your websites. If all of these steps are finished, the .htaccess file will be placed in the same directory in which you can see some folders, including wp-content, wp-includes and wp-admin.

At this time, you can load the websites to check whether the problem has been resolved. If it does, it shows that you fix the internal server error. By the way, please guarantee that you go to Setting-Permalinks to click the save button.

If this solution does not work, you need to do another work, increasing the PHP memory limit.

The PHP Memory Limit Increasing

If you suffer from the limit of PHP memory limit, the internal server error may occur. Among all of the ways to increase the PHP memory limit, we will introduce one of the simplest ways to you. The only thing you need to do is to open your wp-config.php located in the root WordPress directory, then add the “define (‘WP_MEMORY_LIMIT’,’64M’)” inside the main php tag. If you find that the error cannot be fixed still, you should contact the host to increase the memory limit for you.

On the other hand, if you see this error only when trying to login the WordPress admin or upload an image, you need to increase the memory limit by the four steps: creating a blank text file as php.ini, pasting the code “memory=64MB”, saving the file and using the FTP to upload it into /wp-admin/ folder.

If increasing the PHP memory limit cannot fix the internal server error, you need check out the following methods.

Deactivating All Plugins

In case of the two above methods cannot handle this issue, the cause of the error may be a specific plugin. At this time, we have to tell webmasters that it is not an easy work to find this out, so you need to deactivate all WordPress plugins.

To deactivate all plugins, there are two channels we are going to bring to webmasters. You can do this job by taking advantage of FTP or phpMyAdmin.

If this way is helpful, it is clear that one of the plugins caused the error, so webmasters can check out the exact plugin and report the error to the plugin author.

Re-uploading Core Files

If deactivating all plugins cannot also help webmasters get rid of the error, you need to re-upload the wp-admin and wp-includes folders. And it is necessary for us to tell webmasters that this method can get the problem resolved if there is file corrupting and it will not remove any information of your websites.

Seeking Assistance from Hosting Provider

On condition that all of the above methods cannot help webmasters deal with the error, you need to contact the hosting provider who is capable of giving a right solution by looking at the server logs.

Leave a Reply

Your email address will not be published. Required fields are marked *