Heroku code=H10 desc="App crashed" - Can't figure out why it's crashing

heroku error code=h14
heroku status=503
heroku h12
state changed from starting to crashed
heroku logs h10
heroku app crashed
heroku h10 app crashed python
heroku(router): at=error code=h10 d

I've been searching around on this one for a while and can't find anything that seems to be applicable in my situation. I've been staring at these logs and I can't see what the problem is.

This has happened during deployments before, but always seemed to resolve itself. Now this just happened on its own (no deployment) and I can't get out of it. Tried reverting back to a previous version of the app, but it appears I'm stuck. I've reset the dyno and have also done a rake db:migrate.

There are some repetitive things in the log, but I just don't know what to read out of them. Anybody have any idea where the problem is? Any guidance would be greatly appreciated. See the logs below.

Jun 18 15:51:54 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99981 measure.table-cache-hit-rate=0.99349
Jun 18 15:52:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="46.165.195.139" dyno= connect= service= status=503 bytes= 
Jun 18 15:52:07 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="178.255.152.2" dyno= connect= service= status=503 bytes= 
Jun 18 15:52:12 snapclass-production app/postgres:  [47-1]  [] LOG:  checkpoint starting: time 
Jun 18 15:52:13 snapclass-production app/postgres:  [48-1]  [] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.000 s, sync=0.000 s, total=0.334 s; sync files=0, longest=0.000 s, average=0.000 s 
Jun 18 15:52:51 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99994 measure.table-cache-hit-rate=0.99997 
Jun 18 15:53:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="95.141.32.46" dyno= connect= service= status=503 bytes= 
Jun 18 15:53:48 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.97826 measure.table-cache-hit-rate=0.99999 
Jun 18 15:54:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="95.211.217.68" dyno= connect= service= status=503 bytes= 
Jun 18 15:54:17 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="205.197.158.210" dyno= connect= service= status=503 bytes= 
Jun 18 15:54:17 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=www.snapclass.com fwd="205.197.158.210" dyno= connect= service= status=503 bytes= 
Jun 18 15:54:25 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=demosidney.snapclass.com fwd="202.46.61.33" dyno= connect= service= status=503 bytes=  
Jun 18 15:54:44 snapclass-production heroku/web.1:  State changed from crashed to starting 
Jun 18 15:54:44 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.98897 measure.table-cache-hit-rate=0.99087 
Jun 18 15:54:48 snapclass-production heroku/web.1:  Starting process with command `bundle exec thin start -R config.ru -e $RAILS_ENV -p 50180` 
Jun 18 15:55:40 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99926 measure.table-cache-hit-rate=0.99996 
Jun 18 15:55:50 snapclass-production heroku/web.1:  Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 
Jun 18 15:55:50 snapclass-production heroku/web.1:  Stopping process with SIGKILL 
Jun 18 15:55:51 snapclass-production heroku/web.1:  Process exited with status 137 
Jun 18 15:55:51 snapclass-production heroku/web.1:  State changed from starting to crashed 
Jun 18 15:55:52 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=demosidney.snapclass.com fwd="119.63.193.130" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:52 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/snapclasses/sat-prep-math/register host=www.snapclass.com fwd="173.199.115.115" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:53 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="23.21.36.78" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:54 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="23.22.98.102" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:54 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="91.109.115.41" dyno= connect= service= status=503 bytes= 
Jun 18 15:56:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="174.34.224.167" dyno= connect= service= status=503 bytes= 

Try following steps:

- git push heroku master # if not done
- heroku run rake db:migrate
- heroku restart

Wait couple of minutes...

Heroku Error Codes, Process exited 2010-10-06T21:51:12-07:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/"� The database has been migrated to Heroku as well with no errors. But when I click on “Open App” get H10 Errors. After researching for hours and days and applying what i could understand i

In my case it was because I was hardcoding the port to be used,

I changed using this, and it worked

app.listen(process.env.PORT || 3000);

First Heroku deploy failed `error code=H10`, heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ Found solution for me here: Heroku + node.js error (Web process failed that heroku dinamicaly sets, which can be accessed with process.env. Up until recently I was able to deploy development build to Heroku and since couple of days ago even out-of-the-box npx create-react-app would fail with H10 code - solution was to ofc deploy the production build like below:

To create a heroku account

 $heroku create

To verify your git configration is well

$git remote -v

Associate a Git repo with an existing application

$heroku git:remote -a herokuapp-name

To perform push to master

$git push heroku master

To get your database to work you will have to migrate to production database

$heroku run bundle exec rake db:migrate

Then restart

heroku restart

finaly browse to your location

Node app on Heroku - getting “Application Error”, 2018-01-24T11:45:29.690322+00:00 heroku[router]: at=error code=H10 desc=“ App crashed” method=GET path="/" host=firetodo.herokuapp� Deploying app on Heroku (code=H10 desc="App crashed") #14. Closed nop33 opened this issue May 23, 2015 · 52 comments Closed

I had the main entry in package.json pointing at the wrong directory. Ensure it is pointed to the build output directory. As for my case, I had the server file in the /bin folder so I set my package.json

{
  "main": "build/bin/www.js"
  "scripts": {
    "start": "node ."
  }
}

Deploying app on Heroku (code=H10 desc="App crashed") � Issue , Deploying app on Heroku (code=H10 desc="App crashed") #14. Closed. nop33 opened this issue on May 23, 2015 � 52 comments. Closed� Hey guys, im having a similar problem after deploying the parse-server ago. trying to login/ signup and I keep getting this. 2016-04-23T21:20:33.968881+00:00 heroku[router]: at=info method=POST path="/parse/1/login" host=intense-hollows-60991.herokuapp.com request_id=5b792331-09c2-49b1-aa4c-48bd18f8f161 fwd="94.11.105.106" dyno=web.1 connect=1ms service=4ms status=403 bytes=466

In my case, I was working with express on ES6 using babel, the babel was imported as devDependency (Heroku ignores devDependencies in production) after including them into dependencies it worked for me.

dependencies": {
    "@babel/register": "^7.8.3",
    "@babel/core": "^7.8.4",
    "@babel/preset-env": "^7.8.4"
}

Crashes on Heroku, error code H10 � Issue #1589 � parse , Just deployed to Heroku and I'm getting this crash error: 2016-04-22T01:31: 53.925057+00:00 heroku[router]: at=error code=H10 desc="App� heroku documentation: H10 - App crashed. This modified text is an extract of the original Stack Overflow Documentation created by following contributors and released under CC BY-SA 3.0

heroku[router]: at=error code=H10 desc=”App crashed” method , 2020–05–17T14:43:36.398942+00:00 heroku[router]: at=error code=H10 desc=” App crashed” method=GET path=”/” host=rainroom.herokuapp.com� 2010-10-06T21:51:07-07:00 heroku[router]: at=info code=H80 desc="Maintenance mode" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes= H81 - Blank app. No code has been pushed to this application. To get rid of this message you need to do one deploy. This is not an error, but we give it a code

Heroku H10-App Crashed Error Code Example, Get code examples like "Heroku H10-App Crashed Error" instantly right heroku router at error code h10 desc app crashed method post path� $ heroku maintenance:on $ heroku open The custom page will be served and your application logs will show an H80 code for that web hit indicating that a maintenance page was served to the user. $ heroku logs -p router -n 1 2010-10-08T17:44:18-07:00 heroku[router]: at=info code=H80 desc="Maintenance mode" method=GET path=/ host=myapp.herokuapp

how to resolve Heroku H10 error for Next js app deplyed to Heroku , heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/ favicon.ico" host=realtylabapp.herokuapp.com� O segundo log mostra logs da View Build Log visto no proprío site do heroku como você mesmo sugerio de verificar. Meu ambiente é o Windows. Eu sugiro que você baixe o meu projeto do GitHub e tente realizar o deployment direto do seu computador para o servidor Heroku de sua conta Heroku para tira possíveis dúvidas. – wladyband 16/06/17

Comments
  • Have you tried contacting heroku's support?
  • There doesn't appear to be a good way to reach their support team anymore. I only see a page for a Critical Support service. Most everything directs back to their Help docs. You used to be able to submit a ticket, but not it looks like the Critical Support is some added service. So I have gone through their docs for some help and come up empty, but haven't contacted their critical support.
  • Check if this solution will work for you package.json misconfig
  • heroku restart was what fixed it for my PHP app. Thanks!
  • heroku restart instantly fixed my Sinatra App. Thank you very much.
  • this worked! thanks for sharing. - heroku run rake db:migrate - heroku restart