pagesource / fusion-components

A collection of React Components built with Emotion.js
https://sape-fusion.herokuapp.com/
MIT License
13 stars 22 forks source link

Heroku url not working #42

Closed vinaymavi closed 6 years ago

vinaymavi commented 6 years ago

Heroku demo url not working - https://sape-fusion.herokuapp.com/ Server logs -

2017-09-10T12:03:05.081161+00:00 app[web.1]: > fusion@1.0.0 heroku-start /app
2017-09-10T12:03:05.081149+00:00 app[web.1]:
2017-09-10T12:03:05.081162+00:00 app[web.1]: > npm run clean && npm run build && next start -p $PORT
2017-09-10T12:03:05.081163+00:00 app[web.1]:
2017-09-10T12:03:09.060391+00:00 app[web.1]:
2017-09-10T12:03:09.060403+00:00 app[web.1]: > fusion@1.0.0 clean /app
2017-09-10T12:03:09.060405+00:00 app[web.1]: > rimraf .next
2017-09-10T12:03:09.060405+00:00 app[web.1]:
2017-09-10T12:03:11.774401+00:00 app[web.1]:
2017-09-10T12:03:11.774412+00:00 app[web.1]: > fusion@1.0.0 build /app
2017-09-10T12:03:11.774413+00:00 app[web.1]: > next build
2017-09-10T12:03:11.774413+00:00 app[web.1]:
2017-09-10T12:03:15.650545+00:00 app[web.1]: > Using external babel configuration
2017-09-10T12:03:15.651812+00:00 app[web.1]: > Location: "/app/.babelrc"
2017-09-10T12:03:30.572760+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/_next/513a7c74-1e35-4d61-92a2-e59aeb97be18/page/chart-components" host=sape-fusion.herokuapp.com request_id=cce6e66e-206b-4851-8e74-0a88fe0cb8f3 fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:03:39.682572+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/coming-soon" host=sape-fusion.herokuapp.com request_id=3ee289b5-e82d-4c51-9b7f-667b10be2609 fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:03:41.274698+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/_next/513a7c74-1e35-4d61-92a2-e59aeb97be18/page/navigation-components" host=sape-fusion.herokuapp.com request_id=4f85b7c4-8d67-421d-9e9b-94593c185d0c fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:04:01.135535+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2017-09-10T12:04:01.135584+00:00 heroku[web.1]: Stopping process with SIGKILL
2017-09-10T12:04:01.315887+00:00 heroku[web.1]: Process exited with status 137
2017-09-10T12:04:01.334017+00:00 heroku[web.1]: State changed from starting to crashed
2017-09-10T12:04:03.219132+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/navigation-components" host=sape-fusion.herokuapp.com request_id=48fe7287-c503-4c3b-8bf5-583d18ff9663 fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:04:04.461041+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/chart-components" host=sape-fusion.herokuapp.com request_id=d82b80e2-bee5-4a6b-ba48-0947f218fd32 fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:05:31.082682+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=sape-fusion.herokuapp.com request_id=4f3bedb3-a68a-4d50-888c-36ce9714609d fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:05:33.789834+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=sape-fusion.herokuapp.com request_id=9ee98cca-bce5-49bd-b21d-b819a3e34308 fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
2017-09-10T12:06:18.606597+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=sape-fusion.herokuapp.com request_id=3c52a473-3e5a-4cee-95bc-52215a81e705 fwd="45.115.105.207" dyno= connect= service= status=503 bytes= protocol=https
sbmadhav commented 6 years ago

@vinaymavi - Takes some time to load, but works for me!

screen shot 2017-09-11 at 8 05 56 am
vinaymavi commented 6 years ago

@sbmadhav not it is working for me also, that time it was not working, logged the ticket just for tracking.