vuepack: App crashed after deployed on Heroku. But it's working in my local.
I just installed this project on my local and deploy it on heroku.
It is working on my local, but crashed on heroku.
2017-08-25T06:30:25.001177+00:00 app[web.1]: > VuePack is running at http://localhost:4000 2017-08-25T06:30:25.001179+00:00 app[web.1]: 2017-08-25T06:31:06.348236+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 2017-08-25T06:31:06.348326+00:00 heroku[web.1]: Stopping process with SIGKILL 2017-08-25T06:31:06.564701+00:00 heroku[web.1]: Process exited with status 137 2017-08-25T06:31:06.578860+00:00 heroku[web.1]: State changed from starting to crashed 2017-08-25T06:35:36.332773+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=webber.herokuapp.com request_id=b2434d56-7222-46e4-822b-11440bbc94a3 fwd="118.163.202.115" dyno= connect= service= status=503 bytes= protocol=https 2017-08-25T06:35:37.269529+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=webber.herokuapp.com request_id=de3f5728-b7d5-4c61-a3e0-4bd2e9911bf1 fwd="118.163.202.115" dyno= connect= service= status=503 bytes= protocol=https
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 17
https://stackoverflow.com/questions/15693192/heroku-node-js-error-web-process-failed-to-bind-to-port-within-60-seconds-of
within server.js change the last line to
server.listen(process.env.PORT || port)
THIS SOLUTION IS FOR GO When you deploy an app through heroku, it does not allow you to specify the port number.
In other words, you can not specify your web service’s port number as 8000 or something else, heroku decides the port number in runtime.
so, you can not use the following code:
What you can do is, getting the runtime port of heroku.
In short, just use the following code:
i have the same get error with deploy python Flask framework web app …
2018-11-06T10:56:20.915305+00:00 heroku[web.1]: Process exited with status 1 2018-11-06T10:56:22.176106+00:00 heroku[router]: at=error code=H10 desc=“App cra shed” method=GET path=“/” host=iris-falahgs.herokuapp.com request_id=296c3c1e-d0 65-4078-bfb3-f18fb3646a6b fwd=“5.10.227.225” dyno= connect= service= status=503 bytes= protocol=https 2018-11-06T10:56:22.707178+00:00 heroku[router]: at=error code=H10 desc=“App cra shed” method=GET path=“/favicon.ico” host=iris-falahgs.herokuapp.com request_id= fee969f5-c2d6-4c01-b324-9b18406a0ac6 fwd=“5.10.227.225” dyno= connect= service= status=503 bytes= protocol=https 2018-11-06T10:57:22.424624+00:00 heroku[router]: at=error code=H10 desc=“App cra shed” method=GET path=“/” host=iris-falahgs.herokuapp.com request_id=57b98894-ce 03-4462-b7b8-541bb16be0aa fwd=“5.10.227.250” dyno= connect= service= status=503 bytes= protocol=https 2018-11-06T10:57:22.849041+00:00 heroku[router]: at=error code=H10 desc=“App cra shed” method=GET path=“/favicon.ico” host=iris-falahgs.herokuapp.com request_id= 6689a968-2be3-4f6c-b364-126f22481521 fwd=“5.10.227.250” dyno= connect= service= status=503 bytes= protocol=https 2018-11-06T10:58:24.491245+00:00 heroku[router]: at=error code=H10 desc=“App cra shed” method=GET path=“/” host=iris-falahgs.herokuapp.com request_id=71870daa-2b 43-4023-b1ea-adf81bc2c25f fwd=“5.10.227.250” dyno= connect= service= status=503 bytes= protocol=https 2018-11-06T10:58:24.895504+00:00 heroku[router]: at=error code=H10 desc=“App cra shed” method=GET path=“/favicon.ico” host=iris-falahgs.herokuapp.com request_id= fd6603ee-df79-4e93-993e-d8060013aaac fwd=“5.10.227.250” dyno= connect= service= status=503 bytes= protocol=https
I am also still having this error, in spite of implementing the above solution