Databases
StackOverflow2013
Postsdbo
POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
    primarykey
    data
    text
    <p>I'm running a Node.js/Express/MongoHQ app on Heroku. It works perfectly locally. When I push to Heroku the root page '/' loads properly and DOES successfully access the MongoHQ DB. Every other route gives me an Internal Server Error and no identifiable error in the Heroku logs. Although if i go to /page/ I do get my app's 500 page to render properly (random...)</p> <p>Is there anything you can think of that could be going wrong here? I thought it was a DB thing but now it seems like a routing thing. I'm happy to provide any code... I thought I'd paste in some of the log though it's super unhelpful to me anways. Any ideas MAJORYL appreciated.</p> <p>Thanks.</p> <p>Log (for basically any route other than '/')</p> <pre><code>2011-10-07T17:27:03+00:00 app[web.1]: 10.94.69.43 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /assets_js/lib/jquery.1.4.2.min.js HTTP/1.1" 304 - "&lt;MYSITE&gt;/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_js/lib/jquery.timeago.js dyno=web.1 queue=0 wait=0ms service=5ms status=304 bytes=0 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_js/lib/jquery.1.4.2.min.js dyno=web.1 queue=0 wait=0ms service=7ms status=304 bytes=0 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_js/lib/iscroll.js dyno=web.1 queue=0 wait=0ms service=3ms status=304 bytes=0 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_css/viewer.css dyno=web.1 queue=0 wait=0ms service=3ms status=304 bytes=0 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_js/utils.js dyno=web.1 queue=0 wait=0ms service=2ms status=304 bytes=0 2011-10-07T17:27:03+00:00 app[web.1]: 10.117.9.191 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /assets_js/lib/iscroll.js HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 app[web.1]: 10.117.11.66 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /assets_css/viewer.css HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_js/mediacreate.js dyno=web.1 queue=0 wait=0ms service=2ms status=304 bytes=0 2011-10-07T17:27:03+00:00 app[web.1]: 10.94.74.117 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /assets_js/mediacreate.js HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/view_dashboard/activecard.js dyno=web.1 queue=0 wait=0ms service=3ms status=304 bytes=0 2011-10-07T17:27:03+00:00 app[web.1]: 10.84.93.33 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /view_dashboard/activecard.js HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/view_dashboard/drawon.js dyno=web.1 queue=0 wait=0ms service=3ms status=304 bytes=0 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/assets_css/dashboard.css dyno=web.1 queue=0 wait=0ms service=3ms status=304 bytes=0 2011-10-07T17:27:03+00:00 app[web.1]: 10.64.155.131 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /view_dashboard/dashboard.js HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 heroku[router]: GET &lt;MYSITE&gt;/view_presentation/cards/cards.js dyno=web.1 queue=0 wait=0ms service=8ms status=304 bytes=0 2011-10-07T17:27:03+00:00 app[web.1]: 10.84.95.29 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /view_presentation/cards/cards.js HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:03+00:00 app[web.1]: 10.64.155.131 - - [Fri, 07 Oct 2011 17:27:03 GMT] "GET /view_presentation/cards/cards.css HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:05+00:00 app[web.1]: 10.64.147.7 - - [Fri, 07 Oct 2011 17:27:05 GMT] "GET /assets_img/graph.gif HTTP/1.1" 304 - "&lt;MYSITE&gt;" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:05+00:00 heroku[router]: &lt;MYSITE&gt;/assets_img/graph.gif dyno=web.1 queue=0 wait=0ms service=6ms status=304 bytes=0 2011-10-07T17:27:05+00:00 app[web.1]: 10.84.95.29 - - [Fri, 07 Oct 2011 17:27:05 GMT] "GET /favicon.ico HTTP/1.1" 500 1682 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1" 2011-10-07T17:27:05+00:00 heroku[router]: GET &lt;MYSITE&gt;/favicon.ico dyno=web.1 queue=0 wait=0ms service=5ms status=500 bytes=1682 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStuddy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt looks like you have your static files misconfigured. Can you post that part of your express configuration? Should look like `app.use(express['static'](__dirname+'/public', {maxAge: 86400000}));` if you're using the boilerplate template.
      singulars
      1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
      1. USJim Schubert
    2. COok cool, i hope you're onto something here. this is my current static dir ` app.use(express.static(__dirname + '/public'));` and then i have 5 folders within that "assets_css, assets_js etc...". The only reason I'm not totally convinced that could be it is when I go to '/' it does seem to pull in all those files properly.
      singulars
      1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
      1. UStuddy
    3. COThe problem seems to be in your routes definition or server.js definition (how to handle favicon.ico). Can you publish those?
      singulars
      1. POHeroku/Node.js - Routing error of some kind causing Internal Server Errors
      1. UStheprogrammer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload