Comments on: .htaccess File Causes 500 Internal Server Error on Network Solutions

By: Harley Stevens

Harley Stevens — Tue, 12 Apr 2011 03:42:45 +0000

Thanks for sharing this. For beginners like me, it is very helpful.

By: web tutorials

web tutorials — Thu, 17 Sep 2009 15:55:37 +0000

great info, got it to work finally.

By: Sean Murphy

Sean Murphy — Wed, 09 Sep 2009 20:09:11 +0000

Awesome, thanks for sharing!

By: Kevin

Kevin — Wed, 09 Sep 2009 19:54:55 +0000

I’ve had some problems with this as well.

Ended up finding two reasons it didn’t work, because I CREATED the file instead of editing it:

1) Upload in ASCII mode
2) Save .htaccess file coded as ANSI

Hope this helps someone

By: Sean Murphy

Sean Murphy — Fri, 03 Apr 2009 16:57:55 +0000

You might like to read this: http://expressionengine.com/forums/viewthread/106390/#541782

From what I have read, your problem could be from the way your scripts handle database connections, or that your host is killing FastCGI processes when it shouldn’t be. Either way, your host should be able to help you fix the problem, and if they can’t you should consider switching hosts.

By: Janis

Janis — Thu, 02 Apr 2009 11:36:04 +0000

Hmmm… OK we have tried literally everything we can think of, including moving to a new linux server (w same hosts). We are now getting 500 ISEs even when trying to load a purely HTML index page. The error log shows the exact same messages as when there was php on the page: FastCGI: comm with (dynamic) server “/var/www/fcgi/php-cgi” aborted: (first read) idle timeout (30 sec) and FastCGI: incomplete headers (0 bytes) received from server “/var/www/fcgi/php-cgi”. Apparently other sites on the same server are not affected. Also, this problem only came up after switch to Linux. Any clues?

By: Sean Murphy

Sean Murphy — Wed, 25 Mar 2009 15:26:43 +0000

Janis,

There are a number of things that can cause an internal server error, but if you have nothing in your .htaccess file it likely isn’t the problem. If your host allows it, I would make sure you have Apache error logging turned on. The error logs generally give you much more information about the actual problem, opposed to the generic 500 error document. You’ll probably also want to look at the error logs for whatever scripts you’re running (PHP, Perl, etc).

By: Janis

Janis — Wed, 25 Mar 2009 13:18:33 +0000

First up on google – well done. We’re getting a 500 internal server error on our site quite frequently since switching to a linux server on Fasthosts. They say it’s a prob with our scripts but the prob seems so random we can’t figure out what prob could actually be. A thought – if you have nothing at all in the htaccess file (our tecchies haven’t gotten around to it) could this be what’s causing the probs?