How to Fix 500 Internal Server Error in WordPress

Posted on

by


500 Internal Server Error

If you are managing a blog for several years, probably you may have seen the 500 Internal Server Error in WordPress at least for a few times. It happens because there is something gone wrong with the configuration with your files and folders hosted in web server. Let’s see how to fix a 500 Internal Server Error in WordPress and get back site working fine like before.

Causes of Internal Server Error

Web server can face internal server errors due to error in establishing database connection, white screen of death and wrong configurations of files and directories.

How to Fix 500 Internal Server Error

In the most known cases 500 Internal Server Error happens when you have corrupt .htaccess file in your WordPress blog. It can be recovered if your blog is affected by .htaccess file. Below is step how to get new and fresh .htaccess file in just few clicks.

Note: Before making changes in WordPress files make a backup of your whole site.

  1. Log in to cPanel and Open Files Manager with Show Hidden File Option Checked.
    (Simply Go to Home Directory with Show Hidden Option)
  2. Navigate to public_html directory.
    (You will see wp-admin, wp-content, wp-includes directories and files there.)
  3. Locate .htaccess file there and rename it to .htaccess_old or something like old file.
  4. Now open a new tab and try to reload your web page. If it is working fine then delete the .htaccess_old file from that directory.

You will see that a new .htaccess file is gets created with fresh configurations. Now old messy codes and gone from old .htaccess file and you have better working WordPress site. If still your issue is not solved then contact your web host provider for the 500 Internal Server Error issue, they will able to solve your problem in a much better way.

Via this guide you can easily solve 500 Internal Server Error in WordPress.

Read related contents by similar tags:


Leave a Reply

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