First Heroku deploy failed `error code=H10`

Question

I deployed my app to Heroku. It's a node.js + express + socket.io app and this is the package.json file

{
  "name": "game_test",
  "author": "Ilya",
  "description": "A test app for our board game",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node app"
  },
  "dependencies": {
    "express": "3.0.6",
    "jade": "*",
    "socket.io" : "*"
  },
 "engines": {
      "node": "0.8.14"
  }
}

This is the log I get:

heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=game-test-1.herokuapp.com fwd=37.26.146.185 dyno= queue= wait= connect= service= status=503 bytes=
heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=game-test-1.herokuapp.com fwd=37.26.146.185 dyno= queue= wait= connect= service= status=503 bytes=

What does it mean?

"App crashed" has the obvious meaning: your app crashed. Look further up in your logs to see why, or `heroku restart` to launch it again so you can watch it crash again. — willglynn, Jan 14 '13 at 17:04
there is 1 answer to this question which has already received 6 upvotes till now... please select that answer as the correct answer of this question. — Rakib, Feb 19 '14 at 06:36
hi @ilyo! Could you approve my answer on this please? It’s 7 years old and keeps helping people :) Thanx! — Martin Schaer, Jul 04 '20 at 14:32

score 253 · Accepted Answer · edited May 23 '17 at 12:34

253

Found solution for me here: Heroku + node.js error (Web process failed to bind to $PORT within 60 seconds of launch)

In my case my app crashed because I was hard setting the PORT, instead of using the port that heroku dinamicaly sets, which can be accessed with process.env.PORT

app.listen(process.env.PORT || 3000, function(){
  console.log("Express server listening on port %d in %s mode", this.address().port, app.settings.env);
});

edited May 23 '17 at 12:34

Community

1
1

answered Jun 08 '13 at 22:40

Martin Schaer

3,645
1
21
26

2

Well, thank you for this solution. I had the exact same problem, and your answer solved my problem after few hours of researches. – LukyVj Sep 23 '14 at 23:37
3

Even 2 years on, this post helped me out when Heroku was crashing. Thanks @Martin Schaer. – Rey Bango Dec 16 '15 at 23:12
2

Exactly it was my problem with java spring boot. Thanks – Mohy Eldeen Sep 21 '17 at 20:31
4

These days most of us are using ES6. So same answer can also be written in ES6 using arrow function. app.listen(process.env.PORT || 3000, () => { console.log("Express server listening on port %d in %s mode", this.address().port, app.settings.env); }); – Hemadri Dasari Sep 06 '18 at 06:07
This happened to me, which was caused by trying to import a library that was not in my package.json file. – Yvan Pearson Apr 04 '19 at 22:10
@ilyo can you approve this answer? It’s seven years old and keeps helping people :) – Martin Schaer Jul 04 '20 at 14:29
Where should the above mentioned line of code be added? – Praveen Kumar-M Nov 08 '20 at 19:32
1

@PraveenKumar-M usually that line goes in the main file of your server (index.js). `app` is an instance of express – Martin Schaer Nov 11 '20 at 23:46
@MartinSchaer It solves my problem. – Sobhani Nov 04 '21 at 18:52
I get `TypeError: this.address is not a function` in `Node V17`. – Timo Feb 06 '22 at 15:05
The improved `string-ish` way is `app.listen(process.env.port || 3000, () => {// port = this.address().port; console.log(`listening in ${app.settings.env} mode`);});` – Timo Feb 06 '22 at 15:09

score 60 · Answer 2 · answered Jan 12 '16 at 14:46

60

I just had a similar issue with my app, I got the issue after a migration of the DB, after trying many options, the one that helped me was this:

heroku restart

(Using Heroku toolbelt for mac)

answered Jan 12 '16 at 14:46

clarenswd

863
9
17

2

I was getting the same error code and mine used to work but this all of a sudden started happening. The "heroku restart" command cleared this up for me. – Mike Feb 20 '16 at 02:51
1

Same thing happened to me after adding New Relic. Restart fixed my issue – Kris Hollenbeck Nov 30 '18 at 13:51
1

It works for me, try this if this is first deploy – ZiaUllahZia Nov 27 '21 at 21:38
My app was working on localhost and if that's the case `heroku restart` is the correct thing to do first. Thanks! – Ian Poston Framer May 13 '22 at 04:08

score 17 · Answer 3 · edited Oct 13 '20 at 19:31

17

I had this issue, the only problem was my Procfile was like this

web : node index.js

and I changed to

web:node index.js

the only problem was spaces

edited Oct 13 '20 at 19:31

Sayandeep Majumdar

301
1
8
19

answered Feb 20 '19 at 15:54

Arian Nargesi

386
3
11

2

Pretty sure the colon needs to be placed like `web: node index.js` and removing that space I show is optional – jasonleonhard Apr 22 '21 at 21:55
Procfile no longer required for Node.js apps. Article Link : https://devcenter.heroku.com/changelog-items/370 – isarojdahal May 30 '22 at 10:45

score 7 · Answer 4 · answered Feb 06 '16 at 13:14

In my case, i found same error because there is version difference of node and npm on my local machine and defined in package.json version.

"engines": {
  "node": "0.8",
  "npm": "1.2.x"
}

when i check using

node --version : v0.10.41
npm --version : 1.4.29

when i update my package.json to

 "engines": {
  "node": "0.10.41",
  "npm": "1.4.29"
}

It works fine :)

score 5 · Answer 5 · answered Apr 28 '17 at 13:18

5

in my case adding process.env.PORT || 3000 to my http server script, resolved. My heroku log reported 'H20' error and 503 http status.

answered Apr 28 '17 at 13:18

Ewertom Moraes

111
1
4

score 4 · Answer 6 · answered Oct 30 '17 at 03:11

4

In my case, my Procfile was pointing to the wrong file (bot.js which I previously used) so once I updated it, the error was gone.

answered Oct 30 '17 at 03:11

Sina Meraji

61
4

score 3 · Answer 7 · answered Jan 13 '15 at 07:57

3

Also check your database connection. I forgot to change my database connection from localhost and this crashed my app once it was pushed to heroku.

answered Jan 13 '15 at 07:57

lindsaymacvean

4,131
2
17
19

score 3 · Answer 8 · edited Oct 01 '19 at 04:53

3

In my case there was no start command in the script section of package.json file. When I created the package.json file with npm init I did not create a start script command. So I went to the package.json file, under scripts I added a new entry:

 "scripts": {
    "start": "node index.js"
  },

Saved it and uploaded to Heroku and it worked

edited Oct 01 '19 at 04:53

Valentin

2,504
1
25
38

answered Sep 30 '19 at 21:54

Mahmoud Awad

63
5

score 3 · Answer 9 · answered Oct 09 '19 at 05:58

3

upon using hapi18, I find taking out the "host" field and setting the port to:

port: process.env.PORT || 5000 did the trick.

answered Oct 09 '19 at 05:58

littlebotrj

33
5

score 3 · Answer 10 · answered Apr 14 '20 at 14:12

3

Old Thread, but I fix this issue by setting PORT constant to process.env.PORT ||

For some weird reason, it wanted to search Env first.

answered Apr 14 '20 at 14:12

Isaac Frank

313
3
12

score 2 · Answer 11 · answered Dec 24 '17 at 18:12

I faced this same problem and none of the answers above helped me. What i did was run:

node --version

and in the package.json add the engines section with your node version:

{
  "name": "myapp",
  "description": "a really cool app",
  "version": "1.0.0",
  "engines": {
    "node": "6.11.1"
  }
}

score 2 · Answer 12 · answered May 02 '18 at 15:54

2

I had a typo

const PORT = process.env.PORT||'8080';

used to be

const PORT = process.env.port||'8080';

answered May 02 '18 at 15:54

Omar

2,494
2
28
54

score 2 · Answer 13 · answered Jun 18 '19 at 16:55

If you locally start node server by nodemon, like I did, and it locally works, try npm start. Nodemon was telling me no errors, but npm start told me a lot of them in a understandable way and then I could solve them by following another posts here. I hope it helps to someone.

score 1 · Answer 14 · answered Oct 13 '17 at 23:03

1

In my own case, i got this error because i refuse to add a Procfile to my node js app and my "main": "app.js" was initially pointing to another js file as main. so doing these chnages get it fixed for me

answered Oct 13 '17 at 23:03

Forest baba

169
4

score 1 · Answer 15 · answered Dec 14 '18 at 22:00

1

In my case, I forgot to set database env for deployment. you can set env by this command (I'm using mLab for MongoDB server)

heroku config:set MONGO_URI='mongodb://address'

answered Dec 14 '18 at 22:00

minjun youn

21
1
7

score 1 · Answer 16 · answered Feb 07 '19 at 22:35

1

For me it was Package.json it was empty from dependencies even though i thought i did install them.. so I had to reinstall them with --save option in the end and verify they were added to the package.json.. and then push it again and it worked.

answered Feb 07 '19 at 22:35

Roman

11
1

score 1 · Answer 17 · answered Feb 19 '19 at 09:54

1

My port was set to config.httpPort which resolves to 80. I fixed it by doing this:

const PORT = process.env.PORT || config.httpPort;

app.listen(PORT, ...)

Thanks a lot, it wasted me a lot of hours last night.

answered Feb 19 '19 at 09:54

Tamal Web

124
7

score 1 · Answer 18 · answered Oct 24 '19 at 19:11

1

In my case I had code=H10 and status=503 because my Procfile:

web: node build/server.js

and I included /build in .gitignore

answered Oct 24 '19 at 19:11

Donovant

2,807
8
39
64

score 1 · Answer 19 · answered Nov 15 '21 at 19:57

1

My start command had env-cmd -f ./config/prod.env node index.js.

after changing to: node index.js it got fixed.

answered Nov 15 '21 at 19:57

Itay Tur

745
11
26

score 1 · Answer 20 · answered Jan 24 '22 at 14:27

1

I got the same issue, the problem was my Profile was like this:

web: gunicorn__init__:app

Notice with the above there was no space between gunicorn and __ init __

instead of web: gunicorn __init__:app

answered Jan 24 '22 at 14:27

Moureen Caroline

159
1
4

score 0 · Answer 21 · edited Mar 20 '19 at 22:15

0

I got the same above error as "app crashed" and H10 error and the heroku app logs is not showing much info related to the error msg reasons. Then I restarted the dynos in heroku and then it showed the error saying additional curly brace in one of the index.js files in my setup. The issue got fixed once it is removed and redeployed the app on heroku.

edited Mar 20 '19 at 22:15

Stephen Kennedy

18,869
22
90
106

answered Sep 06 '17 at 06:40

Praveen

37
7

score 0 · Answer 22 · answered Jan 20 '18 at 06:33

0

Password contained a % broke it for me.

answered Jan 20 '18 at 06:33

Nash Worth

2,456
1
18
27

score 0 · Answer 23 · edited Mar 20 '19 at 22:15

0

The H10 error code could mean many different things. In my case, the first time was because I didn't know that Heroku isn't compatible with Sqlite3, the second time was because I accidentally pushed an update with Google analytics working in development as well as production.

edited Mar 20 '19 at 22:15

Stephen Kennedy

18,869
22
90
106

answered Mar 20 '19 at 21:53

Trevor Hauck

25
3

score 0 · Answer 24 · answered Apr 02 '19 at 13:38

0

Older thread, but for me I didn't set my .env vars in the Heroku console.

answered Apr 02 '19 at 13:38

Josh Lavely

318
1
3
10

score 0 · Answer 25 · answered Jun 13 '19 at 06:35

0

i was using body-Parser that throw exception

const bodyParser = require('body-Parser')    
//Bodyparser Middleware
app.use(bodyparser.json())

intead of using

    //Bodyparser Middleware
    app.use(express.json())

this resolved my issue

answered Jun 13 '19 at 06:35

S.Sid

1,302
3
15
29

score 0 · Answer 26 · answered Sep 12 '19 at 18:02

I want to register here what was my solution for this error which was a simple file not updated to Github.

I have a full stack project, and my files are structured both root directory for backend and client for the frontend (I am using React.js). All came down to the fact that I was mistakenly pushing the client folder only to Github and all my changes which had an error (missing a comma in a object's instance in my index.js) was not updated in the backend side. Since this Heroku fetches all updates from Github Repository, I couldn't access my server and the error persisted. Then all I had to do was to commit and push to the root directory and update all the changes of the project and everything came back to work again.

score 0 · Answer 27 · answered Jan 13 '20 at 23:18

I struggle with the same error for hours, but I was able to solve it. I installed multer and aws-sdk as a devDependencies by mistake, instead of just dependencies. So, anyone who has the same error, just double-check your package.json file.

Also, a small tip for the property of the engine in package.json.

enter code here
//The greater or equal operators will make sure that you use the right node 
//version 
//even if your current node is greater version than npm node

"engines": {
"node": ">= 0.8.14"
},


//insted of
"engines": {
  "node": "0.8.14"
}

score 0 · Answer 28 · answered Jun 12 '20 at 11:37

0

I was deploying python Django framework when I got this error because I forget to put my app name web: gunicorn plaindjango.wsgi:application --log-file - instead of plaindjango

answered Jun 12 '20 at 11:37

Talha Anwar

1,853
2
14
36

score 0 · Answer 29 · answered Feb 05 '21 at 05:20

For me, I had things unnecessarily split into separate folders. I'm running plotly dash and I had my Procfile, and Pipfile (and lock) together, but separate from the other features of my app (run.py and app.py, the actual content of the pages being used was in a subfolder). So joining much of that together repaired my H10 error

score 0 · Answer 30 · answered Mar 09 '22 at 11:00

0

// PORT
const PORT = process.env.PORT || 8081;

// Listen on port 8081
app.listen(PORT, () =>
  console.log(`Application is listening on port ${PORT}!`)
);

process.env.PORT will handle whatever port is needed on, for example, Heroku, AWS etc.

answered Mar 09 '22 at 11:00

Clancinio

484
1
7
25

score 0 · Answer 31 · answered Mar 14 '22 at 11:40

In my case it was due to the heap memory limit.

Just add some of the dependencies to the dev dependencies object.
Remove unused modules.

You can see the exact error using heroku restart and if it is the memory limit, then upgrade your heroku account.

score 0 · Answer 32 · answered Jun 01 '22 at 13:24

0

in my case the problem solved by changing the order : From : app.listen(2000 || process.env.PORT); to : app.listen(process.env.PORT || 2000);

answered Jun 01 '22 at 13:24

othmane-be

42
5

First Heroku deploy failed `error code=H10`

32 Answers32

Linked