Interesting. Without making any modifications to your app I have it working on heroku: http://safe-harbor-9177.herokuapp.com http://safe-harbor-9177.herokuapp.

Interesting. Without making any modifications to your app I have it working on heroku: http://safe-harbor-9177.herokuapp.com http://safe-harbor-9177.herokuapp.com Here's the full output: https://gist.github.com/speedmanly/1099b37338745ccb5a26 https://gist.github.com/speedmanly/1099b37338745ccb5a26 Adding a Procfile is generally recommended (although heroku will add a default one) web: bundle exec rails server thin -p $PORT -e $RACK_ENV Setting your rails env is a good idea too: heroku config:add RAILS_ENV=production Note I didn't perform those steps to get the app running, they are just recommended. Edit: Actually I do see this line in my heroku logs: 2013-03-21T00:50:21+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 32752 -e $RAILS_ENV` 2013-03-21T00:50:22+00:00 app[web.1]: bash: bin/rails: No such file or directory Adding a Procfile should fix that. Listing 'thin' (or another rails server, e.g. unicorn,puma) in your Gemfile is a good practice as well.