HostingRails.com

Hi there - yeah this usually means you forgot to comment out the AddHandler fcgi line at the top of the .htaccess of the rails app.  Give that a try and let me know how it goes.

Cheers,
~William

Thanks for that, William. I've now got past that using your suggestion (don't remember seeing it in the instructions... I'll check).

Now my Rails app is "failing to start".

My app is on Rails version 1.1.6 according to environment.rb. The server is on version 1.2.2 according to "# rails -v".

I suppose this is where "freezing gems" comes in.

Would it make more sense to upgrade the app now to 1.2.2 and then freeze it? If so, how?

You could upgrade to 1.2.2 - essentially all you need to to is make it so in your environment.rb.  Later you could run rake gems:freeze  once things are set.

For the failed to start error, check out these threads.

http://www.hostingrails.com/forums/wiki_thread/15
http://www.hostingrails.com/forums/wiki_thread/9

Cheers,

~William

I have set the environment to Rails 1.2.2 but now I'm getting this error when I browse to the site:

---
We're sorry, but something went wrong.

We've been notified about this issue and we'll take a look at it shortly.
---

The app loads ok when I do:
# ruby script/console production

Hmm - if you developed on 1.1.6 you should stick with it.  If you really want to move up please email support with the URL in question and we'll take a look and see if we can help.  

Cheers,

~William