Databases
StackOverflow2013
Postsdbo
POError running Node.js app on Heroku
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError running Node.js app on Heroku
    primarykey
    data
    text
    <p>I'm getting a frustrating "error" while trying to run a simple Node.js app on Heroku. Heroku itself is not reporting an error - the app is up (not crashed, no "Hxx" codes being shown); what I get is this: </p> <pre><code>heroku[router]: at=info method=GET path=/index.html host=realsheek.herokuapp.com fwd="24.63.82.165" dyno=web.1 connect=0ms service=4ms status=404 bytes=33 </code></pre> <p>When i run the app from the browser, it says <code>Cannot GET</code>. I don't know what it's trying to <code>GET</code>. My app is a test bed for a SocialProvider using Mozilla's SocialAPIs. The app itself is a version of the demo from <code>https://github.com/mixedpuppy/socialapi-demo</code>. A couple of bugs were fixed, else this is identical to this demo (i used the repo as is with just the bugs fixed). I have an <code>index.html</code> page which installs the SocialProvider, at which time the server-side app kicks in and does the rest of the magic. It runs fine on <code>localhost</code>, but when I push it up to Heroku, it fails. There were no problems reported with the <code>git push</code> (just the usual "no readme data" warnings).</p> <p>I am stumped as I just can't see what it's trying to GET; obviously a 404 error suggests a missing page, but the app makes no calls to any <code>HTML</code> pages, and everything that's needed is present (as my run on <code>localhost</code> confirms).</p> <p>I realize that this isn't a lot to go on, not seeing the actual app and not knowing what it's trying to do. And with no actual error to report - just a 404 status, it obviously could be anything. But I am stumped currently, so if anyone has any insight or suggestion, I'd be most grateful.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBlender
    1. USLew
    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. This table or related slice is empty.
    1. CO**Update:** I used a _LiveHTTPHeaders_ tool to inspect the headers and a GET is issued and nothing is returned (well, a 404 status). I'm starting to suspect that the Heroku server setup is not like a conventional or popular Web server, where it's set up to deliver a `index.html` or `default.html` file in response to a GET with just the path. Instead, it feels like Heroku enables you to create whatever kind of server configuration you want, and does nothing "by default". I'm thinking that the reason I get a 404 is I'm not actually returning anything - and it's my responsibility to do so.
      singulars
      1. POError running Node.js app on Heroku
      1. USLew
    2. CO**Update (cont'd)**: So in my `Node.js` app, as well as creating a server and listening to the outside, i also need to serve a static HTML page for the user to see. If there's someone who knows Heroku and can confirm this, it will set me on the right track to develop the solution. Thank you.
      singulars
      1. POError running Node.js app on Heroku
      1. USLew
 

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