Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
gordillo99 opened this issue Jun 10, 2016 · 4 comments

Comments

@gordillo99
Copy link

Hello,

first of all thanks for this. it's awesome and I hope I can use it for my future projects :) I'm having a problem deploying to Heroku. I was wondering if you could help me :/ it seems the port cannot be resolved? I added the deploy.js script and the script instructions on the package.json as you said on your article. Could you please take a look at my server.js file? thanks in advance! (I just started with web dev)

https://github.com/gordillo99/fixo

@gordillo99
Copy link
Author

and here's the output:

2016-06-10T03:20:48.811226+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-06-10T03:20:48.811419+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-06-10T03:20:49.686488+00:00 heroku[web.1]: Process exited with status 137
2016-06-10T03:20:49.702684+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-10T03:20:57.706265+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fixo.herokuapp.com request_id=dc920794-499f-4508-a08b-4ed40255eb21 fwd="184.66.39.229" dyno= connect= service= status=503 bytes=
2016-06-10T03:20:58.369882+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fixo.herokuapp.com request_id=44d3dd8c-37f6-43d7-afab-36ea41fd903d fwd="184.66.39.229" dyno= connect= service= status=503 bytes=

@christianalfoni
Copy link
Owner

Hi @gordillo99 , yeah, in Heroku go to settings and add a new "config var":

key
NODE_ENV

value
production

That should do it :)

@Odywan55
Copy link

Can any-body advice me the way of handling server changes, with no rerun the server manualy,
and working with routes on it, thanks a lot !!

@hahasecu
Copy link

hahasecu commented Aug 4, 2018

I had the same error. I changed the port as below, and it works

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants