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.

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

See original GitHub issue

My bot often crashes for the following error:

Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
Stopping process with SIGKILL
State changed from starting to crashed
State changed from crashed to starting
Process exited with status 137

Is it a bug within node-slack-client or some settings with heroku that I’m missing? According to this StackOverflow thread, you can fix it by telling your app to listen to a port that Heroku assign dynamically app.listen(process.env.PORT). But how can you do it with slack-client?

My code is here.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

9reactions
iostreamer-Xcommented, Jan 6, 2016

Had the exact issue with my bot on heroku. I just added a server that heroku could bind to and it worked perfectly.

http = require 'http'
handle = (req, res) -> res.end "hit"

server = http.createServer handle

server.listen process.env.PORT || 5000
1reaction
khanh-nguyencommented, May 4, 2015

I got it working. Turn out it must be an app.

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 ...
I had this issue and fixed it. It's a binding error between keystone server and heroku configuration. It means that you're not listening...
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 >
Error R10 Boot timeout Web process failed to bind to $PORT ...
Error R10 Boot timeout Web process failed to bind to $ PORT within 60 seconds of launch. 1.9K views 6 months ago.
Read more >
Web process failed to bind to $PORT within 60 seconds of ...
I was using gunicorn, and the issue seems to be that gunicorn did not bind itself to the port provided by heroku in...
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