Godaddy 500 Internal Server Error Solution


Godaddy 500 Internal Server Error Solution


   One of my site use Drupal 6 on Godaddy Linux share webhosting.  Why use Godaddy? its quite cheap DNS management quite good and plus I stuck with them, but resently Godaddy 500 Internal Server Error keep appear when try to access or open some page... dont have clue on what have trigger this "500 Internal Server Error"... 


I try to search the solution for this Godaddy 500 Internal Server Error Solution, but no luck till this article point me on how to overcome the 500 Internal server Error.  Keep in mind that I dont have the luxury to access the Godaddy shere web hosting log files to know what exactly happen on my site and why the Internal Server Error keep appearing, and base from this post on Godaddy FAST CGI need to be disable...


Make some search about the Godaddy FAST CGI... and  "FAST CGI" itself have good thing and have bad thing (read this what is FAST CGI thing)... and its come to conclusion that only one php.ini or if use php5 (php5.ini) allow, and need to do something to .htaccess for Drupal that sit inside subdomain or directory.


The 500 internal server Error look like in my Godaddy Drupal 6 hosting.

Godaddy 500 Internal Server Error Solution

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.


Solution Godaddy 500 Internal Server Error on my site...

1.  make sure there is only one php5.ini or php.ini in your site and it should be in root directory only... remove all php.ini that may be reside inside your subdomain directry (happen to me)

2.  if you put your drupal inside directory other then root directory, for example inside subdomian directory make sure the .htaccess inside the directory look like below


# Various rewrite rules.
<IfModule mod_rewrite.c>
RewriteEngine on
# If your site is running in a VirtualDocumentRoot at,
# uncomment the following line:
RewriteBase /          <--remove the hash (#)


Note: This work for me... and I hope its work for other too :-)


read this:

Thanks to:


keywords: godaddy 500 internal server error solution, godaddy 500 internal server error, godaddy internal server error, solution godaddy 500 internal server error, godaddy fast cgi, godaddy fast cgi solution




Hi, Thanks for the tips. I’m

Thanks for the tips. I’m having a similar problem with 500-Internal Server Error. In my case it happens in what I call critical hours. This error occurs every hour and in the minutes 25 – 35 and 45 -60. Which are too much minuts with page down. I created a new php.ini and set the value memory = 80 Mb. I haven’t tried the second option. I have contacted Godaddy several times by mail and phone, downloaded numerous tutorials from web search No solution… Any ideas to solve this problem?


Godaddy New Hosting Error Solved By Yor Info

Thanks friend, I used to have so many domains with Godaddy and today bought hosting too.

My drupal installation is 6.x and except front page it returned above horrible server error

Just changed htaccess and viola all headache gone in seconds

All it took less that 2 minutes to reach you site, thanks to Google, here an making corection.


500 error on front page redirect

Issue Summary
Here is my situation. I have my dev version of the site on godaddy economy shared linux hosting and that works perfectly fine.

My production live site is on godaddy ultimate shared hosting on linux. I have the same code base on both these places. But the production site is throwing internal server error 500 from the past 3 days. I have the login destination and front page modules installed and this 500 error happens only when users login and being redirected to a different landing page.
I set up such that anonymous users go to and when logged in on this page, they get redirected to

This setup works perfectly fine on the dev site, but in production, I am getting the 500 error when the redirect to landing happens. Once this error is thrown, if I just type any other url of the site, I am getting to those pages fine.

The only difference between the dev and production site is the data in the DB. Both the sites were working fine for many months now and this 500 error has been happening since last 3 days only. Obviously, the godaddy tech support is of no help. THey just said they did some apache update on all servers 3 days ago and have been adamant that it has nothing to do with my issue, but the timing of when my issue started is so close to this update.
They are suggesting I move the site to a different server to test. I am a bit nervous about this and don't want to lose any prod data.

I am getting frustrated with this. Anybody else have this issue? PLEASE HELP. This is what I see in the error log

[Fri Sep 30 10:20:26 2011] [error] [client] Premature end of script headers: index.php
[Fri Sep 30 10:21:10 2011] [warn] [client] mod_fcgid: read data timeout in 40 seconds
[Fri Sep 30 10:21:10 2011] [error] [client] Premature end of script headers: index.php
[Fri Sep 30 10:56:53 2011] [error] [client] Premature end of script headers: index.php
[Fri Sep 30 11:21:37 2011] [error] [client] Script timed out before returning headers: index.php

What also beats me is that once I get the 500 error on the landing page, I can go to any other page (since I know their paths). So, I thought the issue is with landing page and changed the setting to redirect to one of the other pages that loaded easily. But, even that page is not loading and it throws 500 error. So, I am thinking this may be due to the front page redirect.


I am also having exactly same

I am also having exactly same issue with godaddy shared hosting since yesterday, In my case I am getting following erros in log.

[Fri Nov 11 06:30:38 2011] [warn] [client] mod_fcgid: read data timeout in 40 seconds
[Fri Nov 11 06:30:38 2011] [error] [client] Premature end of script headers: index.php

I have tried reuploading all the drupal files, cleared the cache tables using sql admin, tried uncommenting rewrite line in htaccess, none of these could bring the site back.

Can any one please help me with your experience?