How to Fix 500 Internal Server Error in WordPress [Easy Step]

Are you facing 500 Internal Server Error while browsing? Do you want to get rid of this, this article might be helpful.

500 internal server error in wordpress

500 internal server error in WordPress not only occurs in WordPress rather it occur in any websites being hosted by a server. Internal Server Error in WordPress is often caused by plugin and theme function.

It is very important to find the cause of the problem before trying to fix the problem.

Your website is working fine today suddenly every page of your site starts showing 500 internal server errors, you must be panicking but don’t worry. I am here to help you with your problem.

How can you fix this Error?

500 internal server errror in wordpress infographics

Before trying fixing your server error problem, suggest you to backup your site in case any other problems might occur while fixing the problem.

Let’s get started.

Solution 1: With .HTACCESS

One common problem occurring this error is due to .htaccess file error.

For fixing it.

  • Open your WordPress root directory.
  • Locate the .htaccess file. Once you find your .htaccess file, rename it with .htaccess.bak (It deletes your .htaccess file)
  • Now go to your WordPress admin area, on the left side panel you can find settings.
  • Go to Settings > permalinks
  • Scroll down to the bottom of the page inside permalinks, and click save changes.

Check your website now, the problem might be fixed.

BLUEHOST HOSTING DEALS: Up to 77% Off Hosting Sale
SITEGROUND HOSTING DEALS: Up to 65% Off Hosting Sale
A2 WEB HOSTING DEALS: Save Upto 63%

Solution 2: Add Code to wp-config file

If your problem doesn’t get fixed by the Solution 1, don’t worry we have other options too.

500 internal server error might have occurred if you had used too many plugins or if the plugins are poorly coded which might have exceeded your server’s PHP memory limit.

For fixing it.

  • Open your WordPress root directory.
  • Locate the wp-config.php file. Open the wp-config.php file on your preferred text editor. (If you don’t have a text editor download Microsoft visual studio code here)
  • Once you open the file in your text editor,
  • Add these codes inside PHP codes
    define(‘WP_MEMORY_LIMIT’,’64M’);
  • Save the file and reupload it to your WordPress root directory.

Check your website now, the problem might be fixed.

If it doesn’t work, remove the code updated in wp_config.php and reupload it.

Solution 3: Reactivating Plugins

Reactivating Plugins with WordPress Login

If both of those solutions didn’t work for you, let’s try some less common solutions.

  • Go to your WordPress admin area and click on plugin from the left side panel.
  • Start deactivating plugins one by one and refresh your website.

If this fixes your problem it was caused due to that plugin, so either remove the plugin or recode it.

Reactivating Plugins with cPanel

If you are unable to go to the WordPress admin area.

  • Go to your WordPress root directory and find a folder named wp-contents.
  • Inside the wp-contents folder locate another folder plugins and rename it with anything you wish. (It removes all plugins from the site.)
  • Refresh your site to check if the problem is gone.

If the problem is not gone make sure you revert all the process above.

If none of these worked for you, once you check for the file formation in your WordPress directory or you should go the hard way, i.e. debug your website.

Once again, before trying any of the above options make sure you backup your site in order to make sure you don’t lose your website.

BLUEHOST HOSTING DEALS: Up to 77% Off Hosting Sale
SITEGROUND HOSTING DEALS: Up to 65% Off Hosting Sale
A2 WEB HOSTING DEALS: Save Upto 63%

7 thoughts on “How to Fix 500 Internal Server Error in WordPress [Easy Step]”

  1. Hi there very cool web site!! Guy .. Beautiful .. Wonderful ..
    I will bookmark your blog and take the feeds also? I am satisfied
    to seek out a lot of helpful info here in the put up, we want develop more strategies in this regard, thank you for sharing.

    . . . . .

Leave a Comment