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

rails the page you were looking for doesn't exist.
everfi the page you were looking for doesn t exist
heroku log
the page you're looking for doesn't exist or has possibly been eaten. edmodo
heroku login with github
heroku admin panel
the page you wanted to visit doesn't exist stash
heroku login id

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

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

The page you were looking for doesn't exist. You may have mistyped , I have been trying to deploy my application in heroku but i have been facing some bug. It says The page you were looking for doesn't exist. You may have mistype the address or ghost opened this issue on Oct 30, 2014 · 4 comments. Closed  yeah having an empty routes.rb file(as in nothing within do and end) was an issue, which is strange since earlier today it wasn't an issue and went to the heroku welcome page, but doesn't matter as one wouldn't want an empty routes.rb anyway – barlop Apr 26 '19 at 18:14

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.

Heroku shows "The page you were looking for doesn't , Heroku shows "The page you were looking for doesn't exist". Hi Alex, I was trying to deploy my app to heroku but getting this error. I tried to access the logs file  Logs are the first place to look when your users report seeing the Heroku error pages. Use the heroku logs command to view the unified event stream for your application and the state of the Heroku platform components supporting your application. In this example, the router tried to serve a page for the app, but the web process is crashed.

I'm using postgresql, and I also had page not showing up on heroku.

This command fixed it:

heroku run rake db:setup

and then

heroku rake db:migrate

I had migrated before, but hadn't done the setup first.

I also had tried setting

config.assets.compile = true

in production.rb, but that made no difference.

Heroku deploy not finding routes : rails, I am trying to deploy my app to Heroku, and I get this error: "The page you were looking for doesn't exist. You may have mistyped the address or the page may  If you really do need to trigger a new deployment you can add a new empty commit, then push to Heroku again: git commit --allow-empty -m "Trigger Heroku deploy after enabling collectstatic" git push heroku master The new empty commit is a regular commit. It has a hash, an author, a timestamp, etc. It will have the same tree as its parent.

Have you tried running in production mode locally? Try rails server -e production and see if you get the same error, which you can then debug. Also make sure you've done heroku rake db:migrate.

Able to publish new rails app to heroku, but not when DB is , In the second instance I go there and get "The page you were looking for doesn't exist. rails new blah cd blah git init git add . git commit -m 'blah' heroku create git Original problem:I'm trying to hit the Algolia Places API, but need to hide my​  You can check the Heroku and mLab status pages to see if the systems have a problem. The most common cause is the uploader phone has some issue connecting to the web. 2020-04-12 16:53:15

In my case it was a missing starting page that did not cause a problem in development mode but did cause the above issue on heroku. The accepted answer on this thread sheds more light.

Ruby on Rails app on Heroku: it shows "The page you were looking , It just goes instead of the usual error page we have on the LAN. So you'll have to watch the logs using heroku logs and fix the issues. An app is born. Our app will eventually live at the url in blue. Heroku doesn’t have any of our actual files yet, so if you go there now, you will get the placeholder page you see on the left.

Error Pages, Logs are the first place to look when your users report seeing the Heroku error pages. Use the heroku logs command to view the unified event  The shadow DOM is another concept which provides support for further web page encapsulation. Any elements within the shadow DOM are not affected by the CSS styles of any other markup on the page, and similarly, any CSS defined within the shadow DOM doesn't affect other elements.

Problem deploying app to Heroku using instructions in video , An error message is showing in the browser that "the page you were looking for doesn't exist." I looked online and it seems that a root route will 

The page you were looking for doesn't exist, After Deploying my first project on heroku. It says "The page you were looking for doesn't exist. You may have mistyped there is no error there 

Comments
  • @widjajayd In your console type "heroku logs" and post the print-out you get.
  • Just so you know your not on your own, I'm suffering from this problem to. Did you ever find the cause?
  • I had this problem. I was working on a contact form on the route of contact-me which i had defined in routes.rb. When i visited the url supplied by heroku (e.g www.example_heroku_url.com/) i got the 404 like you. it was because i hadn't defined a root path or index view. so when i visited www.example_heroku_url.com/contact-me It worked. Really silly mistake but thought i'd share in case it helps someone
  • I had the same problem remaining even with assets compilation set as above. A deeper look at bundle log from heroku showed that the only warning was a suggestion to add gem rails_12factor. Surprisingly, it helps. This is rails 4.0.1 ruby 2.0.0, but still could help for someone?
  • For rails 4+ you need to include "gem 'rails_12factor' in your gemfile. Also need to be sure to use postgres for production instead of sqlite3: group :development do gem 'sqlite3' end group :production do gem 'pg' end gem 'rails_12factor'
  • Downvoting. You shouldn't be breaking asset precompilation in production; rather, you should be fixing the problem.
  • @MarnenLaibow-Koser well what's your better idea?
  • @barlop Heroku now runs rake assets:precompile as part of deployment. That part should just work.
  • Great answer, rails server -e production helped me narrow it down.
  • yeah having an empty routes.rb file(as in nothing within do and end) was an issue, which is strange since earlier today it wasn't an issue and went to the heroku welcome page, but doesn't matter as one wouldn't want an empty routes.rb anyway
  • yeah having an empty routes.rb file(as in nothing within do and end) was an issue. I guess i'd have got Rails welcome page locally.. And if i'd make no commit and not pushed any commit to Heroku, i'd get the Heroku welcome page. But here i'd had no route and made a commit and pushed it to Heroku. So yeah, while i'd have got the local rails welcome page, I got that error from Heroku