I 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, webmaster@yoursite.com.com 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.
Here is what you need to do :
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,
Kevin
Author comments are in a darker gray color for you to easily identify the posts author in the comments
Comments are closed since this post is older than 30 days. However, you can continue this discussion in our popular Blogging Forums
hi..
thanks for sharing
Hi Kevin – Good tip. A 500 error usually means a messed up .htaccess. However, when you said “For whatever reason, the .htaccess file can become corrupt” – I chuckled because in my experience, 9 times out of 10 it’s not a plugin or the software that corrupts it, it’s because somebody has been tinkering with it
That’s a fair point Cliff, it is usually the blogger who causes this.
I wrote that because that is exactly what has happened to me both times. I was in the middle of writing an article and it got corrupt. I’m still not sure what caused it.
I always have this message, I thought from the server. Thanks for solution