question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Web process failed to bind to $PORT within 60 seconds of launch

See original GitHub issue

When I deploy a Telegram bot built with this module to Heroku, after 60 seconds I get following error:

2016-09-20T11:50:11.599886+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-09-20T11:50:11.599886+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-09-20T11:50:11.705966+00:00 heroku[web.1]: Process exited with status 137

I couldn’t find a way to set a port because there is no .listen(...) method when calling the Telegram constructor. Any ideas?

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:7
  • Comments:8

github_iconTop GitHub Comments

31reactions
rmnblmcommented, Sep 20, 2016

I solved the problem by using a Procfile with the following content:

worker: node index.js

I did also run the following command

$ heroku scale web=0 worker=1
13reactions
vincentaudebertcommented, Nov 28, 2017

Watch out. This doesn’t work on a free dyno.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Heroku + node.js error (Web process failed to bind to $PORT ...
Heroku + node. js error (Web process failed to bind to $PORT within 60 seconds of launch) - Stack Overflow. Stack Overflow for...
Read more >
Error R10 Boot timeout Web process failed to bind to $PORT ...
Hi everyone, in this video I go over the main issues I had while trying ... Web process failed to bind to $PORT...
Read more >
Error R10 (Boot timeout) -> Web process failed to bind to ...
Heroku Deployment - Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch #3994.
Read more >
Why is my app crashing with an R10 error? - Heroku Help
R10 - Boot timeout errors occur when a web process took longer than 60 seconds to bind to its assigned $PORT . This...
Read more >
Heroku + node.js error (Web process failed to bind to $PORT ...
Node.js – Heroku + node.js error (Web process failed to bind to $PORT within 60 seconds of launch). herokunode.js. I have my first...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found