I am trying to execute the application but i am facing NPM errors in the log.What might be the reason.
2017-02-14T17:57:20.698084+00:00 app[web.1]: npm ERR! Or if that isn't
available, you can get their info via:
2017-02-14T17:57:20.697188+00:00 app[web.1]: npm ERR! not with npm
itself. 2017-02-14T17:57:20.697375+00:00 app[web.1]: npm ERR! Tell the
author that this fails on your system:
2017-02-14T17:57:20.697706+00:00 app[web.1]: npm ERR! You can get
information on how to open an issue for this project with:
2017-02-14T17:57:20.698436+00:00 app[web.1]: npm ERR! There is likely
additional logging output above. 2017-02-14T17:57:20.698248+00:00
app[web.1]: npm ERR! npm owner ls Sap-api-ai
2017-02-14T17:57:20.717695+00:00 app[web.1]: npm ERR! Please include
the following file with any support request:
2017-02-14T17:57:20.831148+00:00 heroku[web.1]: State changed from
starting to crashed 2017-02-14T17:57:20.777084+00:00 heroku[web.1]:
Process exited with status 1 2017-02-14T17:58:48.330160+00:00
heroku[router]: at=error code=H10 desc="App crashed" method=GET
path="/" host=sap-api-ai-google.herokuapp.com
request_id=db57d06b-4cd6-41f8-aaf6-6688e0603f97 fwd="49.206.119.184"
dyno= connect= service= status=503 bytes=
2017-02-14T17:58:49.862288+00:00 heroku[router]: at=error code=H10
desc="App crashed" method=GET path="/favicon.ico"
host=sap-api-ai-google.herokuapp.com
request_id=665fc337-8aec-46ec-914a-3e6b0990a2b5 fwd="49.206.119.184"
dyno= connect= service= status=503 bytes=
Hard to say without seeing your code, but if I had to guess you're binding a static port rather than letting Heroku set your port for you via the PORT environment variable.
If you have something like:
app.listen(3000, (e) => { console.log('Connected!'); });
Then you'll want to change out that port number for the variable:
app.listen(process.env.PORT || 3000, (e) => { console.log('Connected!'); });
Related
I have a small project that I have been working on that can be found here.
The project was originally vanilla HTML, CSS and JavaScript, but I have been working on converting it to React in a feature branch.
I tried to deploy the branch to Heroku, which appears to be successful, however when I try to visit the application, it gives me an Application error. When I check the logs, it is outputting like so
2022-01-19T02:45:57.270692+00:00 app[web.1]: npm ERR!
2022-01-19T02:45:57.270731+00:00 app[web.1]: npm ERR! Failed at the meapi#1.0.0 start script.
2022-01-19T02:45:57.270767+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-19T02:45:57.275755+00:00 app[web.1]:
2022-01-19T02:45:57.275856+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-19T02:45:57.275902+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-19T02_45_57_271Z-debug.log
2022-01-19T02:45:57.405061+00:00 heroku[web.1]: Process exited with status 1
2022-01-19T02:45:57.506577+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-19T02:45:58.536667+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=magicedenfloortracker.herokuapp.com request_id=92ecc3ce-83c0-497a-8453-06a7abf9f9f1 fwd="152.208.11.3" dyno= connect= service= status=503 bytes= protocol=https
2022-01-19T02:45:58.762210+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=magicedenfloortracker.herokuapp.com request_id=b1d68b37-1cbb-4245-825b-0ebe77fa6f90 fwd="152.208.11.3" dyno= connect= service= status=503 bytes= protocol=https
I'm not quite sure what to make of these error logs though. Since the path to the create-react-app folder isn't standard, I tried to create a Procfile and set web: cd .\floor-track\ && npm start thinking that it might cd into the folder then run npm start first, but I am not sure that is working as I expected.
Any tips on resolving this issue?
Additionally, outside of the react folder, I have a file 'api.js' that I would like to run hourly (uses node cron) but I am not sure how to run this file in the background on heroku. Is this possible as well?
Thanks in advance!
This question already has answers here:
Heroku failing to start my node app because its trying to do it with nodemon
(4 answers)
Closed last year.
if I run the application from terminal, it is working, I mean that it is running in the browser.
The problem is when I try to host it on Heroku. My app has Backend: Nodejs with Express and Database: MySQL.
I see that I have errors, but I don't understand them and I've tried multiple things to make it work, but I can't.
Logs from the error:
2022-01-14T11:42:19.516824+00:00 app[web.1]:
2022-01-14T11:42:19.516835+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T11:42:19.516835+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:42:19.516835+00:00 app[web.1]:
2022-01-14T11:42:19.520231+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:42:19.524055+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:42:19.524197+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:42:19.524258+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:42:19.524466+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:42:19.526613+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T11:42:19.526650+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:42:19.526699+00:00 app[web.1]: npm ERR!
2022-01-14T11:42:19.526737+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T11:42:19.526788+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:42:19.532863+00:00 app[web.1]:
2022-01-14T11:42:19.532933+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:42:19.532983+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T11_42_19_527Z-debug.log
2022-01-14T11:42:19.647800+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:42:19.723822+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:42:22.997860+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=867758f1-1252-4674-a7cc-261fbe9f98d1 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:42:23.312967+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=5cb55772-dad6-486d-bc15-d37731d94661 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:46:57.000000+00:00 app[api]: Build started by user daviddserb#yahoo.com
2022-01-14T11:47:11.000000+00:00 app[api]: Build succeeded
2022-01-14T11:47:11.297457+00:00 app[api]: Deploy 7ee73460 by user daviddserb#yahoo.com
2022-01-14T11:47:11.297457+00:00 app[api]: Release v4 created by user daviddserb#yahoo.com
2022-01-14T11:47:12.210235+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T11:47:14.084097+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T11:47:15.244156+00:00 app[web.1]:
2022-01-14T11:47:15.244170+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T11:47:15.244170+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:47:15.244170+00:00 app[web.1]:
2022-01-14T11:47:15.248738+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:47:15.254959+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:47:15.255206+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:47:15.255316+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:47:15.255405+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:47:15.259050+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T11:47:15.259107+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:47:15.259167+00:00 app[web.1]: npm ERR!
2022-01-14T11:47:15.259216+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T11:47:15.259274+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:47:15.266461+00:00 app[web.1]:
2022-01-14T11:47:15.266545+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:47:15.266590+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T11_47_15_260Z-debug.log
2022-01-14T11:47:15.397039+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:47:15.454442+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:47:18.779406+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=325e420b-9e58-4f7e-bad0-4872dc699fe0 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:47:19.023207+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=e081eb63-0cff-4e27-a710-1d60cbc9beb1 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:48:40.000000+00:00 app[api]: Build started by user daviddserb#yahoo.com
2022-01-14T11:48:53.770119+00:00 app[api]: Deploy 7fc9ef13 by user daviddserb#yahoo.com
2022-01-14T11:48:53.770119+00:00 app[api]: Release v5 created by user daviddserb#yahoo.com
2022-01-14T11:48:54.000000+00:00 app[api]: Build succeeded
2022-01-14T11:48:54.117745+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T11:48:55.999691+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T11:48:56.952415+00:00 app[web.1]:
2022-01-14T11:48:56.952427+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T11:48:56.952428+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:48:56.952428+00:00 app[web.1]:
2022-01-14T11:48:56.962683+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:48:56.968511+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:48:56.968735+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:48:56.968786+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:48:56.968886+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:48:56.972412+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T11:48:56.972521+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:48:56.972620+00:00 app[web.1]: npm ERR!
2022-01-14T11:48:56.972734+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T11:48:56.972822+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:48:56.977729+00:00 app[web.1]:
2022-01-14T11:48:56.977829+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:48:56.977880+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T11_48_56_974Z-debug.log
2022-01-14T11:48:57.123929+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:48:57.256711+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:49:03.042405+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=40e7bba7-b78d-4472-b652-c1b296a4343a fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:49:03.312210+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=4b214bf1-4d44-4895-8bc7-2d8cc34e172d fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:51:59.531549+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=c38f2d45-f1a5-43a9-9f4e-e2f34ef4d1bb fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:51:59.801198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=a5c7fb1c-5ce3-4ccf-81ac-3cb8fdce759f fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:56:02.383069+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=22db8c3d-1714-42f8-a40f-9e02d0cc737a fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:56:02.634499+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=fc256052-006a-4289-a836-ce8094e64944 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T12:05:20.233183+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T12:05:22.754848+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T12:05:23.970064+00:00 app[web.1]:
2022-01-14T12:05:23.970078+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T12:05:23.970079+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T12:05:23.970079+00:00 app[web.1]:
2022-01-14T12:05:23.973595+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T12:05:23.978419+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T12:05:23.978592+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T12:05:23.978667+00:00 app[web.1]: npm ERR! file sh
2022-01-14T12:05:23.978764+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T12:05:23.981475+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T12:05:23.981519+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T12:05:23.981564+00:00 app[web.1]: npm ERR!
2022-01-14T12:05:23.982264+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T12:05:23.982320+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There
is likely additional logging output above.
2022-01-14T12:05:23.984901+00:00 app[web.1]:
2022-01-14T12:05:23.984998+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T12:05:23.985048+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T12_05_23_982Z-debug.log
2022-01-14T12:05:24.128019+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T12:05:24.211507+00:00 heroku[web.1]: State changed from starting to crashed
I don't know what else to give you, so please, if you need some other files or information about my project, let me know and I will upload them.
Seems like you are using "nodemon". Probably if you installed with "npm i -g nodemon"
you can see that error. So nodemon installed on your pc but your project have not nodemon. Just run npm i nodemon in your terminal while located project. Finally deploy again. And i'm sorry about bad english.
I deployed a Heroku app using the CLI. The code is based in JS(Node).
The log displayed the following message-
2020-11-19T18:13:19.981359+00:00 heroku[web.1]: State changed from crashed to starting
2020-11-19T18:13:32.577655+00:00 heroku[web.1]: Starting process with command `npm start`
2020-11-19T18:13:35.931851+00:00 app[web.1]:
2020-11-19T18:13:35.931868+00:00 app[web.1]: > server#1.0.0 start /app
2020-11-19T18:13:35.931868+00:00 app[web.1]: > concurrently "npm run server" "npm run client"
2020-11-19T18:13:35.931869+00:00 app[web.1]:
2020-11-19T18:13:35.941884+00:00 app[web.1]: sh: 1: concurrently: not found
2020-11-19T18:13:35.951483+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-11-19T18:13:35.951777+00:00 app[web.1]: npm ERR! syscall spawn
2020-11-19T18:13:35.952007+00:00 app[web.1]: npm ERR! file sh
2020-11-19T18:13:35.952258+00:00 app[web.1]: npm ERR! errno ENOENT
2020-11-19T18:13:35.957255+00:00 app[web.1]: npm ERR! server#1.0.0 start: `concurrently "npm run server" "npm run client"`
2020-11-19T18:13:35.957411+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-11-19T18:13:35.957579+00:00 app[web.1]: npm ERR!
2020-11-19T18:13:35.957727+00:00 app[web.1]: npm ERR! Failed at the server#1.0.0 start script.
2020-11-19T18:13:35.957859+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-11-19T18:13:35.968472+00:00 app[web.1]:
2020-11-19T18:13:35.968693+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-11-19T18:13:35.968767+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-11-19T18_13_35_958Z-debug.log
2020-11-19T18:13:36.042215+00:00 heroku[web.1]: Process exited with status 1
2020-11-19T18:13:36.100527+00:00 heroku[web.1]: State changed from starting to crashed
2020-11-19T18:41:07.000000+00:00 app[api]: Build started by user riteshkumarstudy#gmail.com
2020-11-19T18:41:43.985964+00:00 app[api]: Deploy 1581c630 by user riteshkumarstudy#gmail.com
2020-11-19T18:41:43.985964+00:00 app[api]: Release v4 created by user riteshkumarstudy#gmail.com
ll be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.
2020-11-19T18:42:59.987409+00:00 app[web.1]: Server listening on port 3001
2020-11-19T18:43:00.110366+00:00 app[web.1]: (node:4) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
2020-11-19T18:43:16.984202+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/" host=pacific-scrubland-58982.herokuapp.com request_id=e41c2163-819d-4d95-a87a-48e84acfd06e fwd="223.225.248.157" dyno= connect= service= status=503 bytes= protocol=https
2020-11-19T18:43:55.839112+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2020-11-19T18:43:55.866993+00:00 heroku[web.1]: Stopping process with SIGKILL
2020-11-19T18:43:56.004273+00:00 heroku[web.1]: Process exited with status 137
2020-11-19T18:43:56.057821+00:00 heroku[web.1]: State changed from starting to crashed
2020-11-19T18:43:56.610979+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-scrubland-58982.herokuapp.com request_id=f941b09d-91ae-4ddb-87c1-96a66d8c8912 fwd="223.225.248.157" dyno= connect= service= status=503 bytes= protocol=https
2020-11-19T18:43:57.136454+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-scrubland-58982.herokuapp.com request_id=be1491ea-8d01-4b37-9902-6e93678ba0b6 fwd="223.225.248.157" dyno= connect= service= status=503 bytes= protocol=https
2020-11-19T18:43:58.163525+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-scrubland-58982.herokuapp.com request_id=c304480a-ca92-4bf0-9ef2-837931f38d55 fwd="223.225.248.157" dyno= connect= service= status=503 bytes= protocol=https
2020-11-19T18:43:58.312956+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-scrubland-58982.herokuapp.com request_id=7334f985-397f-4f3e-b667-99fd19831635 fwd="223.225.248.157" dyno= connect= service= status=503 bytes= protocol=https
The link to the repo is https://github.com/CSAIDept/Final-Combined-Pages
Need help on what to do next?
I used the https://github.com/mars/create-react-app-buildpack to deploy this app.
You installed concurrently as a dev dependency, Heroku will not install devDependency. Try adding concurrently to normal dependency in package.json and try again
Trying to deploy Node.js app on heroku but getting following errors. Can anyone help me with where am I going wrong.
2018-06-29T00:01:21.641247+00:00 app[web.1]: npm ERR!
2018-06-29T00:01:21.641578+00:00 app[web.1]: npm ERR! Failed at the v1#1.0.0 start script.
2018-06-29T00:01:21.641895+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging
output above.
2018-06-29T00:01:21.660378+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-06-29T00:01:21.659090+00:00 app[web.1]:
2018-06-29T00:01:21.660779+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-06-29T00_01_21_645Z-debug.log
2018-06-29T00:01:21.758849+00:00 heroku[web.1]: State changed from starting to crashed
2018-06-29T00:01:21.736544+00:00 heroku[web.1]: Process exited with status 1
2018-06-29T00:01:22.688914+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=campground-.herokuapp.com
request_id=7b46f802-439e-4038-85f4-882fbd765417 fwd="139.94.66.0"
dyno= connect= service= status=503 bytes= protocol=https
2018-06-29T00:01:23.464401+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico"
host=campground-.herokuapp.com
request_id=fe27806a-8390-431f-ba14-233625c388cf fwd="139.94.66.0"
dyno= connect= service= status=503 bytes= protocol=https
2018-06-29T00:09:27.204098+00:00 heroku[web.1]: State changed from crashed to starting
2018-06-29T00:09:32.209782+00:00 heroku[web.1]: Starting process with command npm start
2018-06-29T00:09:35.411423+00:00 app[web.1]:
2018-06-29T00:09:35.411450+00:00 app[web.1]: > v1#1.0.0 start /app
2018-06-29T00:09:35.411452+00:00 app[web.1]: > node app.js
2018-06-29T00:09:35.411454+00:00 app[web.1]:
enter image description here
I get the following error wile trying to run the app after deployment to Heroku. I can't figure out what the error is as the deployment was a success.
2017-08-08T19:58:15.400596+00:00 app[web.1]: npm ERR! node ./bin/www
2017-08-08T19:58:15.400766+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2017-08-08T19:58:15.400935+00:00 app[web.1]: npm ERR! npm bugs watchhours
2017-08-08T19:58:15.401099+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2017-08-08T19:58:15.401267+00:00 app[web.1]: npm ERR! npm owner ls watchhours
2017-08-08T19:58:15.401434+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2017-08-08T19:58:15.407305+00:00 app[web.1]:
2017-08-08T19:58:15.407919+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2017-08-08T19:58:15.408104+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2017-08-08T19:58:15.497534+00:00 heroku[web.1]: State changed from starting to crashed
2017-08-08T19:58:15.483131+00:00 heroku[web.1]: Process exited with status 1
2017-08-08T19:58:28.070249+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=watch-hours.herokuapp.com request_id=08648f85-8ff8-4496-a1d0-4a59b656394b fwd="117.214.91.103" dyno= connect= service= status=503 bytes= protocol=https
2017-08-08T19:58:28.710982+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=watch-hours.herokuapp.com request_id=348cafa0-abb3-411f-a460-fdc52165e94f fwd="117.214.91.103" dyno= connect= service= status=503 bytes= protocol=https
If you login to heroku you can see the logs for your project... your error will most likely be in there: https://dashboard.heroku.com/apps/you-app-name/logs