Well, bluehost is back at it again, this time they installed 2.3.3 1
day after 2.3.2 and put in a bunch of new gems, including rack. Fcgi
stopped working again and here is the quick steps I took to fix it.
Hopefully bluehost will make systemwide changes instead of making us
all install local gems to fix their mistakes

This is the workaround I cam up with
http://jibwa.com/code-and-documentation-for-programmers/more-bluegost-fcgi-issues-with-rails-2.3.3-and.html

Here is a ticket I entered for lighthouse... maybe the conversation
will continue there.
https://rails.lighthouseapp.com/projects/8994/tickets/2941-233-fcgi-problem

On Jul 19, 6:09 ¨Âí¬ Êïóè ¼êïóèâ÷è®®®Àçíáéì®ãïí¾ ÷òïôåº
> I was running into similar issues. Mine was due to an old .htaccess
> file. I put together the info I got, plus a yet to be posted rails
> install update for bluehost athttp://jibwa.com/code-and-documentation-for-programmers/bluehost-rail...
> .
>
> On Jul 15, 7:49 ¨Âí¬ ÒïçåÐáãë ¼òïçåòðáãë²®®®Àçíáéì®ãïí÷òïôåº
>
>
>
> > Saurabh Agarwal wrote:
> > > Hi All,
>
> > > I am getting 500 error while deploying to bluehost , please provide some
> > > pointer
>
> > Pointer 1
> > don't deploy to bluehost
> > pointer 2
> > if you must, then here's how I did it.http://betterlogic.com/roger/?p=368
> > =r
> > --
> > Posted viahttp://www.ruby-forum.com/.