Error R10 (Boot timeout) - when trying to run on Heroku.

[mrobinson537]

Hey guys,

First off, this sample project is awesome - so thank you for putting in the time! After playing with it for a while, I decided to try pushing my slightly customized version (mostly client changes) up to Heroku. The deploy itself went fine, along with the build and better-npm-run start script. Everything looks fine with the normal logging appearing from the server. After 60 sec however, the app crashes and tries to restart - then just repeats this loop over and over again. Here is what the logs look like:
2017-05-18T22:04:31.699139+00:00 app[web.1]: [0] > [email protected] start-prod /app 2017-05-18T22:04:31.699140+00:00 app[web.1]: [0] > better-npm-run start-prod 2017-05-18T22:04:31.699140+00:00 app[web.1]: [0] 2017-05-18T22:04:31.790695+00:00 app[web.1]: [0] running better-npm-run in /app 2017-05-18T22:04:31.805558+00:00 app[web.1]: [0] Executing script: start-prod 2017-05-18T22:04:31.805563+00:00 app[web.1]: [0] 2017-05-18T22:04:31.805996+00:00 app[web.1]: [0] to be executed: node ./bin/server.js 2017-05-18T22:04:36.622830+00:00 app[web.1]: [0] ---- 2017-05-18T22:04:36.622845+00:00 app[web.1]: [0] ==> ✅ React Redux Example is running, talking to API server on 3030. 2017-05-18T22:04:36.622845+00:00 app[web.1]: [0] ==> 💻 Open http://localhost:8080 in a browser to view the app. 2017-05-18T22:05:28.861369+00:00 app[web.1]: Error waiting for process to terminate: No child processes 2017-05-18T22:05:28.837505+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 2017-05-18T22:05:28.837626+00:00 heroku[web.1]: Stopping process with SIGKILL 2017-05-18T22:05:28.981496+00:00 heroku[web.1]: Process exited with status 22 2017-05-18T22:05:28.992124+00:00 heroku[web.1]: State changed from starting to crashed 2017-05-18T22:05:30.109694+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=my-app.herokuapp.com request_id=57bb44c0-d5ff-4fc2-b335-3ec30e20e5d7 fwd="184.70.193.170" dyno= connect= service= status=503 bytes= protocol=https ...

There could be simple solution for this (and I hope there is) that I am not seeing. I may just not understand the whole configuration well enough. But here's where I'm at:

So, my guess is that this has to do with the fact it appears to be trying to run on http://localhost:8080 instead of my Heroku apps URL. I've tried to track down where I might fix this, and made small changes attempting to fix it, but haven't succeeded at this point.

I tried editing the webpack.definePlugin function in prod.config.js file to include my Heroku host url, and an API_PORT of 0.0.0.0. After some googling, I read that Heroku doesn't like when you try to force a specific PORT. Here's what that looked like:
new webpack.DefinePlugin({ 'process.env': { NODE_ENV: '"production"', APIHOST: '"https://my-app.herokuapp.com/"', APIPORT: '"0.0.0.0"' }, ...
I tried tinkering with the whole config setup but haven't yet found a way around the Error R10 (Boot timeout) coming from Heroku. Do you have any thoughts or suggestions? Any help would be greatly appreciated.

Thank you for taking the time to read this.
Cheers!