I recently posted a question on a similar topic. I did a major overhaul of everything on the URL, and the same thing happened as last time: I could deploy everything and run it using heroku local web
. When I went to the web dyno, it said I had an application error and I then check the logs. Here is what it said (I am using a project on github called atwork):
2017-05-02T01:16:25.212121+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2017-05-02T01:16:25.212255+00:00 app[web.1]: npm ERR! npm bugs AtWork
2017-05-02T01:16:25.212392+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2017-05-02T01:16:25.212520+00:00 app[web.1]: npm ERR! npm owner ls AtWork
2017-05-02T01:16:25.212654+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2017-05-02T01:16:25.216026+00:00 app[web.1]:
2017-05-02T01:16:25.216224+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2017-05-02T01:16:25.216336+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2017-05-02T01:16:25.293193+00:00 heroku[web.1]: State changed from starting to crashed
2017-05-02T01:16:25.280920+00:00 heroku[web.1]: Process exited with status 1
2017-05-02T01:16:35.053137+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=room111-thoughts.herokuapp.com request_id=d6424fde-9eb4-42d7-b18c-2e7577701513 fwd="108.221.62.78" dyno= connect= service= status=503 bytes= protocol=https
What I found weird was that there was no real explanation of the error. Here is the link to the project (I didn't change anything except for the mongodb connection URI). I can provide any other needed information.
via I am a registered user
No comments:
Post a Comment