-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Description
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
- You've met the prerequisites.
- You're running the latest version of Parse Server.
- You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
Steps to reproduce
Logs/Trace
2016-03-26T18:44:47.180056+00:00 app[web.1]: npm ERR! node ./bin/parse-server
2016-03-26T18:44:47.180209+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-03-26T18:44:47.180525+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-03-26T18:44:47.180673+00:00 app[web.1]: npm ERR! npm owner ls parse-server
2016-03-26T18:44:47.180824+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-03-26T18:44:47.184164+00:00 app[web.1]:
2016-03-26T18:44:47.184378+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-03-26T18:44:47.184516+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-03-26T18:44:47.866568+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-26T18:54:11.699191+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=eshopper1.herokuapp.com request_id=7b152146-2e47-4aa8-8895-ea270bea089f fwd="59.177.194.145" dyno= connect= service= status=503 bytes=