How To Fix The WordPress Internal Server Error

WordPressI was writing an article earlier today on Blogging Tips and I received the famous Internal Server Error. When this happens you can still access non WordPress pages on your site and see your favicon however the site is unusable and you cannot access any pages, including the WordPress admin area,

This is the kind of message you will see if you have an Internal Server Error :

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

9 times out of 10, this is a simple htaccess problem and is easily resolved. For whatever reason, the .htaccess file can become corrupt (perhaps due to a plugin however many things could cause it). So all you have to do is correct your .htaccess file and you should be able to see your site again.

How To Fix The WordPress Internal Server Error

Here is what you need to do :

  1. Back up your current .htaccess file.
  2. Delete all of the information from your .htaccess file and save it i.e. upload a blank .htaccess file.
  3. Your blog should now be usable again so go into the admin area and set your permalink structure again.
  4. Open your new working .htaccess file in an editor. Now copy over all the non WordPress .htaccecss information from your old backed up .htaccess file eg. any search engine htaccess information, ip blocks etc – basically everything Non-WordPress that you added before.

If you find that adding all the code from the previous .htaccess file is causing an Internal Server Error again then remove it all and enter the information back to the working .htaccess file line by line to see what is causing the problem.

Bear in mind, this might not resolve every Internal Server Error you get though if you suddenly get this error on your WordPress blog, this is the first thing I recommend doing before contacting your host or looking for an alternative solution.

Best of luck,

  • 9
  • 9

Disclosure: In full disclosure, it is safe to assume that the site owner is benefiting financially or otherwise from everything you click on, read, or look at while on my website. This is not to say that is the case with all content, as all publications on the site are original and written to provide value and references to our audience.


  1. iman July 6, 2009
  2. Cliff Leonard July 6, 2009
  3. Kevin Muldoon July 6, 2009
  4. Abu Farhan July 14, 2009
  5. sam September 4, 2010
  6. Abhishek September 15, 2010
  7. znupii September 19, 2010
  8. Peter October 22, 2010
  9. Mike November 10, 2010
  10. sami ben gharbia November 29, 2010
  11. A Morris December 27, 2010
  12. Victor January 19, 2011
  13. andrewgoldy February 4, 2011
  14. jiri February 22, 2011
  15. sachin March 1, 2011
  16. alex March 24, 2011
  17. Willie March 27, 2011
  18. Dipa jasa web April 1, 2011
  19. sagive May 5, 2011