youngheart12
commented
5 years ago was able to fixed this error .Small mistake at my start script in package.json at server side. if you too get this error just make little correction in script "scripts":{ "start":"node server.js" } instead of "scripts":{ "start":"server.js" }
heroku logs --tail 2019-07-25T02:55:06.000000+00:00 app[api]: Build succeeded 2019-07-25T02:55:16.913162+00:00 heroku[web.1]: Starting process with command
npm start2019-07-25T02:55:19.977235+00:00 heroku[web.1]: State changed from starting to crashed 2019-07-25T02:55:19.990612+00:00 heroku[web.1]: State changed from crashed to starting 2019-07-25T02:55:19.804585+00:00 app[web.1]: 2019-07-25T02:55:19.804608+00:00 app[web.1]: > mern_shopping_list@1.0.0 start /app 2019-07-25T02:55:19.804610+00:00 app[web.1]: > server.js 2019-07-25T02:55:19.804611+00:00 app[web.1]: 2019-07-25T02:55:19.813734+00:00 app[web.1]: sh: 1: server.js: not found 2019-07-25T02:55:19.819664+00:00 app[web.1]: npm ERR! file sh 2019-07-25T02:55:19.820012+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2019-07-25T02:55:19.820288+00:00 app[web.1]: npm ERR! errno ENOENT 2019-07-25T02:55:19.820532+00:00 app[web.1]: npm ERR! syscall spawn 2019-07-25T02:55:19.822058+00:00 app[web.1]: npm ERR! mern_shopping_list@1.0.0 start:server.js2019-07-25T02:55:19.822244+00:00 app[web.1]: npm ERR! spawn ENOENT 2019-07-25T02:55:19.822482+00:00 app[web.1]: npm ERR! 2019-07-25T02:55:19.822660+00:00 app[web.1]: npm ERR! Failed at the mern_shopping_list@1.0.0 start script. 2019-07-25T02:55:19.822857+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2019-07-25T02:55:19.834828+00:00 app[web.1]: 2019-07-25T02:55:19.835052+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2019-07-25T02:55:19.837652+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-07-25T02_55_19_824Z-debug.log 2019-07-25T02:55:19.956624+00:00 heroku[web.1]: Process exited with status 1 2019-07-25T02:55:29.592888+00:00 heroku[web.1]: Starting process with commandnpm start2019-07-25T02:55:32.533679+00:00 heroku[web.1]: State changed from starting to crashed 2019-07-25T02:55:32.513740+00:00 heroku[web.1]: Process exited with status 1 2019-07-25T02:55:32.403818+00:00 app[web.1]: 2019-07-25T02:55:32.403843+00:00 app[web.1]: > mern_shopping_list@1.0.0 start /app 2019-07-25T02:55:32.403846+00:00 app[web.1]: > server.js 2019-07-25T02:55:32.403847+00:00 app[web.1]: 2019-07-25T02:55:32.417052+00:00 app[web.1]: sh: 1: server.js: not found 2019-07-25T02:55:32.439267+00:00 app[web.1]: npm ERR! file sh 2019-07-25T02:55:32.439518+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2019-07-25T02:55:32.439706+00:00 app[web.1]: npm ERR! errno ENOENT 2019-07-25T02:55:32.439891+00:00 app[web.1]: npm ERR! syscall spawn 2019-07-25T02:55:32.441150+00:00 app[web.1]: npm ERR! mern_shopping_list@1.0.0 start:server.js2019-07-25T02:55:32.441289+00:00 app[web.1]: npm ERR! spawn ENOENT 2019-07-25T02:55:32.441466+00:00 app[web.1]: npm ERR! 2019-07-25T02:55:32.441601+00:00 app[web.1]: npm ERR! Failed at the mern_shopping_list@1.0.0 start script. 2019-07-25T02:55:32.441747+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2019-07-25T02:55:32.451180+00:00 app[web.1]: 2019-07-25T02:55:32.451313+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2019-07-25T02:55:32.451380+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-07-25T02_55_32_443Z-debug.log 2019-07-25T02:55:33.386189+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=iremember-v1.herokuapp.com request_id=c64028b2-c25d-459d-8830-a356aebaaa9c fwd="157.42.123.187" dyno= connect= service= status=503 bytes= protocol=https 2019-07-25T02:55:34.160617+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=iremember-v1.herokuapp.com request_id=d756329d-ae44-453b-8b28-40b814bdf186 fwd="157.42.123.187" dyno= connect= service= status=503 bytes= protocol=https