Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Heroku problem : The page you were looking for doesn't exist

I have followed book until chapter 5 finished and it's working OK in my linux workstation when I push to Heroku, all data pushed correctly but when I try to open Heroku (http://vivid-sky-685.heroku.com)

I get a 404 message.

The page you were looking for doesn't exist. You may have mistyped the address or the page may have moved.

Below is my Gemfile for application

source 'http://rubygems.org' gem 'rails', '3.0.5' gem 'sqlite3'  group :development do   gem 'rspec-rails', '2.5.0' end  group :test do   gem 'rspec', '2.5.0'   gem 'webrat', '0.7.1'   gem 'spork', '0.9.0.rc4' end  gem 'rake','~> 0.8.7' 

Any ideas what could be going wrong?

@odin here is my heroku logs , thanks

2011-09-11T10:41:57+00:00 heroku[router]: GET vivid-sky-685.heroku.com/y dyno=web.1 queue=0 wait=0ms service=5ms status=404 bytes=728 2011-09-11T10:41:57+00:00 app[web.1]:  2011-09-11T10:41:57+00:00 app[web.1]:  2011-09-11T10:41:57+00:00 app[web.1]: Started GET "/y" for 93.186.31.80 at 2011-09-11 03:41:57 -0700 2011-09-11T10:41:57+00:00 app[web.1]:  2011-09-11T10:41:57+00:00 app[web.1]: ActionController::RoutingError (No route matches "/y"): 2011-09-11T10:41:57+00:00 app[web.1]:    2011-09-11T10:41:57+00:00 app[web.1]:  2011-09-11T10:41:57+00:00 app[web.1]:  2011-09-11T10:41:57+00:00 heroku[nginx]: 93.186.31.80 - - [11/Sep/2011:03:41:57 -0700] "GET /y HTTP/1.1" 404 728 "-" "Mozilla/5.0 (BlackBerry; U; BlackBerry 9300; en) AppleWebKit/534.8+ (KHTML, like Gecko) Version/6.0.0.546 Mobile Safari/534.8+" vivid-sky-685.heroku.com 2011-09-11T11:45:28+00:00 heroku[web.1]: Idl  2011-09-11T11:45:29+00:00 heroku[web.1]: State changed from up to down 2011-09-11T11:45:29+00:00 heroku[web.1]: State changed from down to created 2011-09-11T11:45:29+00:00 heroku[web.1]: State changed from created to starting 2011-09-11T11:45:30+00:00 heroku[web.1]: Stopping process with SIGTERM 2011-09-11T11:45:30+00:00 app[web.1]: >> Stopping ... 2011-09-11T11:45:30+00:00 heroku[web.1]: Process exited 2011-09-11T11:45:30+00:00 heroku[web.1]: Starting process with command `thin -p 16738 -e production -R /home/heroku_rack/heroku.ru start` 2011-09-11T11:45:33+00:00 app[web.1]: >> Thin web server (v1.2.6 codename Crazy Delicious) 2011-09-11T11:45:33+00:00 app[web.1]: >> Maximum connections set to 1024 2011-09-11T11:45:33+00:00 app[web.1]: >> Listening on 0.0.0.0:16738, CTRL+C to stop 2011-09-11T11:45:33+00:00 heroku[web.1]: State changed from starting to up 2011-09-11T12:53:00+00:00 heroku[web.1]: Idling 2011-09-11T12:53:01+00:00 heroku[web.1]: State changed from up to down 2011-09-11T12:53:02+00:00 heroku[web.1]: Stopping process with SIGTERM 2011-09-11T12:53:02+00:00 app[web.1]: >> Stopping ... 2011-09-11T12:53:02+00:00 heroku[web.1]: Process exited 2011-09-11T13:18:21+00:00 heroku[rake.1]: State changed from created to starting 2011-09-11T13:18:23+00:00 app[rake.1]: Awaiting client 2011-09-11T13:18:23+00:00 app[rake.1]: Starting process with command `bundle exec rake db:migrate`   2011-09-11T13:18:26+00:00 heroku[rake.1]: Process exited 2011-09-11T13:18:26+00:00 heroku[rake.1]: State changed from up to complete 2011-09-11T13:20:02+00:00 heroku[web.1]: Unidling 2011-09-11T13:20:02+00:00 heroku[web.1]: State changed from down to created 2011-09-11T13:20:02+00:00 heroku[web.1]: State changed from created to starting 2011-09-11T13:20:04+00:00 heroku[web.1]: Starting process with command `thin -p 48393 -e production -R /home/heroku_rack/heroku.ru start` 2011-09-11T13:20:06+00:00 app[web.1]: >> Thin web server (v1.2.6 codename Crazy Delicious) 2011-09-11T13:20:06+00:00 app[web.1]: >> Maximum connections set to 1024 2011-09-11T13:20:06+00:00 app[web.1]: >> Listening on 0.0.0.0:48393, CTRL+C to stop 2011-09-11T13:20:07+00:00 heroku[web.1]: State changed from starting to up 2011-09-11T13:20:07+00:00 app[web.1]:  2011-09-11T13:20:07+00:00 app[web.1]:  2011-09-11T13:20:07+00:00 app[web.1]: Started GET "/" for 118.137.144.220 at 2011-09-11 06:20:07 -0700 2011-09-11T13:20:08+00:00 app[web.1]:  2011-09-11T13:20:08+00:00 app[web.1]: ActionController::RoutingError (uninitialized constant PagesController): 2011-09-11T13:20:08+00:00 app[web.1]:    2011-09-11T13:20:08+00:00 app[web.1]:  2011-09-11T13:20:08+00:00 app[web.1]:  2011-09-11T13:20:08+00:00 heroku[router]: GET vivid-sky-685.heroku.com/ dyno=web.1 queue=0 wait=0ms service=403ms status=404 bytes=728 2011-09-11T13:20:08+00:00 heroku[nginx]: 118.137.144.220 - - [11/Sep/2011:06:20:08 -0700] "GET / HTTP/1.1" 404 728 "-" "Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0" vivid-sky-685.heroku.com 
like image 550
widjajayd Avatar asked Sep 11 '11 07:09

widjajayd


People also ask

Why am I getting application error on Heroku?

"Application Error" or similar is always caused by your own application code. Routing errors will normally only surface themselves within the logs of your application. In most cases, you will be able to see the cause of the error there. To learn more about logging, please see our Logging article on DevCenter.

What is 503 error Heroku?

Whenever your app experiences an error, Heroku will return a standard error page with the HTTP status code 503. To help you debug the underlying error, however, the platform will also add custom error information to your logs.

How to see error on Heroku?

You can view logs with the Heroku CLI, the dashboard, your logging add-on, or in your log drain. You can't view logs for apps in Shield spaces with Private Space Logging enabled.

Why am I seeing application error?

However, most application errors occur because developers either unknowingly introduce logic errors into their code or do not discover potential problems during an application's test phase. Viruses and faulty hardware are also causes of application errors.


2 Answers

I know it's an old problem but I ran into it too. I realized I didn't change the root route in config/routes.rb before pushing. Not changing it might result in a welcome page locally, but on heroku it will get the above error.

like image 183
xji Avatar answered Sep 20 '22 15:09

xji


I got the same problem; however, after changing 1 line code of production.rb located in config/environments/production.rb from

config.assets.compile = false 

to

config.assets.compile = true 

commit the new change. Then my sample app works fine on heroku

like image 26
Tony Nguyen Avatar answered Sep 21 '22 15:09

Tony Nguyen