CODEWITHSUNDEEP
node.jsheroku
fivepointseven
fivepointseven

Reputation: 1051

Heroku Node.js Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch

I found a dozen solutions for Express powered apps with setting port to listen on. But I have an app that doesn't use Express and doesn't in fact listens anything. And after 60 seconds of it successfully running I get a Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch message. How I can get around it? Thanks.

Upvotes: 23

Views: 35243

Answers (6)

WaterTrash
WaterTrash

Reputation: 438

This comment solved my issue: https://stackoverflow.com/a/67787556/8684435

The issue is the way you define the port, it always runs on 3001 which is not possible on Heroku, you need to bind the $PORT env variable. Change your code to check the first fi the process.env.PORT is defined (it will be on Heroku but on your local dev environment it will default to 3001)

app.listen(process.env.PORT || 3001, '0.0.0.0', () => {
  console.log("Server is running.");
});

Upvotes: 2

Mali Gautam H
Mali Gautam H

Reputation: 21

I also got the same the same problem: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch

flowing work in my pc windows 10 visual studio code

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

also added these three line in package.json

"worker": "node index.js", "start": "node index.js" "test": "node test.js"

Upvotes: 0

Ferry Sanjaya
Ferry Sanjaya

Reputation: 224

I have the same issue:

Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch

I tried many things.

The following works without using express:

http.createServer(onRequest).listen(process.env.PORT || 6000)

Upvotes: 0

Pille
Pille

Reputation: 1133

Another way would be changing the dynos from web (standard setting regardless of the settings in Procfile) to worker with these commands:

heroku ps:scale web=0
heroku ps:scale worker=1

Sometimes Heroku ignores settings in the Procfile.

Upvotes: 24

sergiy.dragunov
sergiy.dragunov

Reputation: 790

If your app doesn't listen any port then you should use another type of app in you Procfile, I mean in Procfile you have: 

web: node app.js

replace it with: 

worker: node app.js

"web" type of application means that your app MUST listen some port

Upvotes: 35

fivepointseven
fivepointseven

Reputation: 1051

After lots of googling I decided to npm install express and add

var express = require('express');
var app     = express();

app.set('port', (process.env.PORT || 5000));

//For avoidong Heroku $PORT error
app.get('/', function(request, response) {
    var result = 'App is running'
    response.send(result);
}).listen(app.get('port'), function() {
    console.log('App is running, server is listening on port ', app.get('port'));
});

This fixed the error, even though I don't like adding express just to avoid one error. If someone finds a better solution, please let me know.

Upvotes: 40

Related Questions