Tried a bunch of reformats on my server.js file. config is put into heroku settings.
Error: Cannot read properties of null (reading 'split')
is what seems to be standing out to me in the logs. Along with the two H10's. I've typed these errors in and tried to change things using the answers I saw on here but still cant get the app to work without the app crash on heroku.
Here are my logs:
2022-06-22T17:25:25.597973+00:00 app[web.1]:
2022-06-22T17:25:25.597982+00:00 app[web.1]: > it-logger-final#1.0.0 start
2022-06-22T17:25:25.597983+00:00 app[web.1]: > node server
2022-06-22T17:25:25.597983+00:00 app[web.1]:
2022-06-22T17:25:25.933187+00:00 app[web.1]: Server running in production mode on port 43811
2022-06-22T17:25:25.933707+00:00 app[web.1]: Error: Cannot read properties of null (reading 'split')
2022-06-22T17:25:26.215915+00:00 heroku[web.1]: Process exited with status 1
2022-06-22T17:25:26.439416+00:00 heroku[web.1]: State changed from starting to crashed
2022-06-22T17:25:28.264639+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=it-logger-motta.herokuapp.com request_id=c5e7c89c-047c-4f11-b52e-337946492e02 fwd="68.134.27.230" dyno= connect= service= status=503 bytes= protocol=https
2022-06-22T17:25:28.553271+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=it-logger-motta.herokuapp.com request_id=cb691fd1-6022-4375-886e-c98520d5ec87 fwd="68.134.27.230" dyno= connect= service= status=503 bytes= protocol=https
Here is my repo: https://github.com/SyntaxMotta/IT-Logger-Final
Related
I have github account which is connnected with my heroku account. I am trying to deploy code through heroku and my project is also connected with heroku pipeline. Build is getting succeeded. But getting error while accessing app
Heroku logs
2022-09-07T10:08:37.346556+00:00 heroku[web.1]: Starting process with command `npm start`
2022-09-07T10:08:41.005367+00:00 app[web.1]:
2022-09-07T10:08:41.005458+00:00 app[web.1]: > food-court#0.0.1 start
2022-09-07T10:08:41.005458+00:00 app[web.1]: > nest start
2022-09-07T10:08:41.005459+00:00 app[web.1]:
2022-09-07T10:08:41.020373+00:00 app[web.1]: /tmp/start-7b018378.sh: 1: nest: not found
2022-09-07T10:08:41.187916+00:00 heroku[web.1]: Process exited with status 127
2022-09-07T10:08:41.284101+00:00 heroku[web.1]: State changed from starting to crashed
2022-09-07T10:13:07.218759+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=food-court-be-dev.herokuapp.com request_id=52c79661-a554-4c2b-b412-c24429d538c5 fwd="103.181.100.29" dyno= connect= service= status=503 bytes= protocol=https
2022-09-07T10:13:07.784604+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=food-court-be-dev.herokuapp.com request_id=f1a47ec4-6160-47d2-80ef-a0db2569d7bf fwd="103.181.100.29" dyno= connect= service= status=503 bytes= protocol=https
Thanks in advance
resolved issue by changing "start": "nest start", to "start": "node dist/main.js" in package.json
Am getting the following error after a successful build and deploy of a JHipster microservice application onto Heroku:
2021-05-11T00:59:56.244858+00:00 app[web.1]: :: JHipster 🤓 :: Running Spring Boot 2.4.4 ::
2021-05-11T00:59:56.244859+00:00 app[web.1]: :: https://www.jhipster.tech ::
2021-05-11T00:59:56.244958+00:00 app[web.1]:
2021-05-11T01:00:32.625226+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/config/saathratrigateway/prod/main" host=saathratri-gateway.herokuapp.com request_id=a8dc6325-ca04-4c1c-a069-fe397dde7a82 fwd="54.227.16.41" dyno= connect= service= status=503 bytes= protocol=https
2021-05-11T01:01:12.399755+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/config/saathratrigateway/prod/main" host=saathratri-gateway.herokuapp.com request_id=f19c6d78-85f8-4e2e-a721-b3f02b83e62d fwd="3.95.223.176" dyno= connect= service= status=503 bytes= protocol=https
2021-05-11T01:01:17.500232+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 90 seconds of launch
2021-05-11T01:01:17.583985+00:00 heroku[web.1]: Stopping process with SIGKILL
2021-05-11T01:01:17.754138+00:00 heroku[web.1]: Process exited with status 137
2021-05-11T01:01:17.838377+00:00 heroku[web.1]: State changed from starting to crashed
2021-05-11T01:01:19.306908+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/config/saathratrigateway/prod/main" host=saathratri-gateway.herokuapp.com request_id=c89c88c7-42dd-4a88-90cf-4f12ab669559 fwd="3.95.223.176" dyno= connect= service= status=503 bytes= protocol=https
Any advice would be greatly appreciated.
My best,
Amar
I do not understand how Jekyll/Heroku can come back with nothing to run - I followed the Jekyll Heroku instructions on the official Heroku docs ( I fixed a favicon error as well) and I just don't know what I'm missing at this point. I then configured the app for Puma & I can't seem to find the solution after checking other S/O posts and googling around.
2018-03-14T16:27:11.274627+00:00 app[web.1]: [4] Puma starting in cluster mode...
2018-03-14T16:27:11.274648+00:00 app[web.1]: [4] * Version 3.11.3 (ruby 2.5.0-p0), codename: Love Song
2018-03-14T16:27:11.274650+00:00 app[web.1]: [4] * Min threads: 8, max threads: 32
2018-03-14T16:27:11.274652+00:00 app[web.1]: [4] * Environment: development
2018-03-14T16:27:11.274654+00:00 app[web.1]: [4] * Process workers: 3
2018-03-14T16:27:11.274655+00:00 app[web.1]: [4] * Phased restart available
2018-03-14T16:27:11.274663+00:00 app[web.1]: [4] ERROR: No application configured, noth
2018-03-14T16:27:11.274627+00:00 app[web.1]: [4] Puma starting in cluster mode...
2018-03-14T16:27:11.274648+00:00 app[web.1]: [4] * Version 3.11.3 (ruby 2.5.0-p0), codename: Love Song
2018-03-14T16:27:11.274650+00:00 app[web.1]: [4] * Min threads: 8, max threads: 32
2018-03-14T16:27:11.274652+00:00 app[web.1]: [4] * Environment: development
2018-03-14T16:27:11.274654+00:00 app[web.1]: [4] * Process workers: 3
2018-03-14T16:27:11.274655+00:00 app[web.1]: [4] * Phased restart available
2018-03-14T16:27:11.274663+00:00 app[web.1]: [4] ERROR: No application configured, nothing to run
2018-03-14T16:27:11.635258+00:00 heroku[web.1]: State changed from starting to crashed
2018-03-14T16:27:13.137740+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=the8-bitblog.herokuapp.com request_id=d5005423-9255-4d6d-983f-db1b80b5dca9 fwd="70.48.185.37" dyno= connect= service= status=503 bytes= protocol=https
2018-03-14T16:27:14.209900+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=the8-bitblog.herokuapp.com request_id=12876663-5bf2-483d-b87b-17c435ef9072 fwd="70.48.185.37" dyno= connect= service= status=503 bytes= protocol=httpsing to run
2018-03-14T16:27:11.635258+00:00 heroku[web.1]: State changed from starting to crashed
2018-03-14T16:27:13.137740+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=the8-bitblog.herokuapp.com request_id=d5005423-9255-4d6d-983f-db1b80b5dca9 fwd="70.48.185.37" dyno= connect= service= status=503 bytes= protocol=https
2018-03-14T16:27:14.209900+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=the8-bitblog.herokuapp.com request_id=12876663-5bf2-483d-b87b-17c435ef9072 fwd="70.48.185.37" dyno= connect= service= status=503 bytes= protocol=https
I recently deployed a rails app and was careful to put my Procfile & Rakefile in root / specify those params but for some reason, it won't start here. Is this an issue with having a free Heroku account (therefore limited workers?) I'm not entirely sure how that extends.
Thanks for any help
Seems like that's fixed but back to favicon errors ... 2018-03-
14T16:54:24.096956+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=the8-bitblog.herokuapp.com request_id=b9345a18-bfb4-4f68-a310-e703f0aa1a3a fwd="70.48.185.37" dyno= connect= service= status=503 bytes= protoc
ol=https
2018-03-14T16:54:24.740532+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=the8-bitblog.herokuapp.com request_id=d8418c31-c457-4b55-862b-9181162e8192 fwd="70.48.185.37" dyno= connect= service= status=503 bytes= protocol=https
I've been trying to launch the Stormpath tutorial app to Heroku, but Heroku is telling me 'An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.'
I checked the logs and the main thing seems to be 'Error: API key ID and secret is required.', but I have no idea what that's supposed to mean. I already followed the guide here https://stormpath.com/blog/build-nodejs-express-stormpath-app and set the key ID and secret in the terminal. What do I do to make this thing launch on Heroku properly?
Everything runs just fine locally and here is the full log:
2016-05-23T00:57:21.912777+00:00 app[web.1]: > node server.js
2016-05-23T00:57:21.912752+00:00 app[web.1]:
2016-05-23T00:57:21.912773+00:00 app[web.1]: > my-webapp#1.0.0 start /app
2016-05-23T00:57:21.912778+00:00 app[web.1]:
2016-05-23T00:57:23.236038+00:00 app[web.1]: error: Error: API key ID and secret is required.
2016-05-23T00:57:23.236061+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:1213:16
2016-05-23T00:57:23.236061+00:00 app[web.1]: at fn (/app/node_modules/async/lib/async.js:746:34)
2016-05-23T00:57:23.236062+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:166:37
2016-05-23T00:57:23.236060+00:00 app[web.1]: at ValidateClientConfigStrategy.process (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:33:12)
2016-05-23T00:57:23.236056+00:00 app[web.1]: at newError (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:15:14)
2016-05-23T00:57:23.236063+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:706:43
2016-05-23T00:57:23.236063+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:167:37
2016-05-23T00:57:23.236065+00:00 app[web.1]: at Immediate._onImmediate (/app/node_modules/async/lib/async.js:1206:34)
2016-05-23T00:57:23.236066+00:00 app[web.1]: at tryOnImmediate (timers.js:534:15)
2016-05-23T00:57:23.236066+00:00 app[web.1]: at processImmediate [as _immediateCallback] (timers.js:514:5)
2016-05-23T00:58:19.594432+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-05-23T00:58:19.594683+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-05-23T00:58:20.928062+00:00 heroku[web.1]: State changed from starting to crashed
2016-05-23T00:58:20.879933+00:00 heroku[web.1]: Process exited with status 137
2016-05-23T00:58:40.721955+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=workpls.herokuapp.com request_id=a8142cf5-0e42-402b-b777-69aa7867808a fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T00:58:41.882687+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=workpls.herokuapp.com request_id=04db8c96-ff75-4535-9aa9-cb1415951742 fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:00:10.489523+00:00 heroku[api]: Release v6 created by brandonlum94#gmail.com
2016-05-23T01:00:10.489494+00:00 heroku[api]: Deploy 7873309 by brandonlum94#gmail.com
2016-05-23T01:00:10.619075+00:00 heroku[slug-compiler]: Slug compilation started
2016-05-23T01:00:10.619085+00:00 heroku[slug-compiler]: Slug compilation finished
2016-05-23T01:00:10.966086+00:00 heroku[web.1]: State changed from crashed to starting
2016-05-23T01:00:12.625037+00:00 heroku[web.1]: Starting process with command `npm start`
2016-05-23T01:00:15.420889+00:00 app[web.1]:
2016-05-23T01:00:15.420908+00:00 app[web.1]: > my-webapp#1.0.0 start /app
2016-05-23T01:00:15.420911+00:00 app[web.1]: > node server.js
2016-05-23T01:00:15.420912+00:00 app[web.1]:
2016-05-23T01:00:16.939751+00:00 app[web.1]: error: Error: API key ID and secret is required.
2016-05-23T01:00:16.939761+00:00 app[web.1]: at newError (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:15:14)
2016-05-23T01:00:16.939763+00:00 app[web.1]: at ValidateClientConfigStrategy.process (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:33:12)
2016-05-23T01:00:16.939764+00:00 app[web.1]: at fn (/app/node_modules/async/lib/async.js:746:34)
2016-05-23T01:00:16.939765+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:1213:16
2016-05-23T01:00:16.939766+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:706:43
2016-05-23T01:00:16.939765+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:166:37
2016-05-23T01:00:16.939767+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:167:37
2016-05-23T01:00:16.939768+00:00 app[web.1]: at Immediate._onImmediate (/app/node_modules/async/lib/async.js:1206:34)
2016-05-23T01:00:16.939769+00:00 app[web.1]: at tryOnImmediate (timers.js:534:15)
2016-05-23T01:00:16.939770+00:00 app[web.1]: at processImmediate [as _immediateCallback] (timers.js:514:5)
2016-05-23T01:01:13.074993+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-05-23T01:01:13.074993+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-05-23T01:01:13.918547+00:00 heroku[web.1]: State changed from starting to crashed
2016-05-23T01:01:13.916299+00:00 heroku[web.1]: Process exited with status 137
2016-05-23T01:01:16.688198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=workpls.herokuapp.com request_id=b8b03962-66f9-4b67-be55-009dff78c8b0 fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:01:17.984769+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=workpls.herokuapp.com request_id=5a6a9d91-a144-415c-9293-951aedc0f26b fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:02:40.694187+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=workpls.herokuapp.com request_id=b004fcf9-f3d8-482f-bae3-3e4cfe90160e fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:02:41.552456+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=workpls.herokuapp.com request_id=80a2b214-7a03-4a32-b09d-7ed210685b1e fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:04:23.179785+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=workpls.herokuapp.com request_id=47a5a69e-b26b-4318-9c34-869a1f488e54 fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:04:24.057028+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=workpls.herokuapp.com request_id=1736845b-b276-435d-ac09-dd308592f290 fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:07:39.697756+00:00 heroku[api]: Release v7 created by brandonlum94#gmail.com
2016-05-23T01:07:39.697756+00:00 heroku[api]: Set STORMPATH_SECRET_KEY config vars by brandonlum94#gmail.com
2016-05-23T01:07:40.390722+00:00 heroku[web.1]: State changed from crashed to starting
2016-05-23T01:07:42.158518+00:00 heroku[web.1]: Starting process with command `npm start`
2016-05-23T01:07:44.211079+00:00 app[web.1]:
2016-05-23T01:07:44.211110+00:00 app[web.1]: > my-webapp#1.0.0 start /app
2016-05-23T01:07:44.211113+00:00 app[web.1]: > node server.js
2016-05-23T01:07:44.211119+00:00 app[web.1]:
2016-05-23T01:07:45.303304+00:00 app[web.1]: error: Error: API key ID and secret is required.
2016-05-23T01:07:45.303317+00:00 app[web.1]: at newError (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:15:14)
2016-05-23T01:07:45.303318+00:00 app[web.1]: at ValidateClientConfigStrategy.process (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:33:12)
2016-05-23T01:07:45.303319+00:00 app[web.1]: at fn (/app/node_modules/async/lib/async.js:746:34)
2016-05-23T01:07:45.303320+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:1213:16
2016-05-23T01:07:45.303320+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:166:37
2016-05-23T01:07:45.303321+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:706:43
2016-05-23T01:07:45.303321+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:167:37
2016-05-23T01:07:45.303322+00:00 app[web.1]: at Immediate._onImmediate (/app/node_modules/async/lib/async.js:1206:34)
2016-05-23T01:07:45.303324+00:00 app[web.1]: at processImmediate [as _immediateCallback] (timers.js:514:5)
2016-05-23T01:07:45.303323+00:00 app[web.1]: at tryOnImmediate (timers.js:534:15)
2016-05-23T01:08:42.173794+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-05-23T01:08:42.173889+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-05-23T01:08:42.972327+00:00 heroku[web.1]: State changed from starting to crashed
2016-05-23T01:08:42.960998+00:00 heroku[web.1]: Process exited with status 137
2016-05-23T01:08:42.973810+00:00 heroku[web.1]: State changed from crashed to starting
2016-05-23T01:08:44.895681+00:00 heroku[web.1]: Starting process with command `npm start`
2016-05-23T01:08:47.490885+00:00 app[web.1]:
2016-05-23T01:08:47.490893+00:00 app[web.1]: > my-webapp#1.0.0 start /app
2016-05-23T01:08:47.490900+00:00 app[web.1]:
2016-05-23T01:08:47.490899+00:00 app[web.1]: > node server.js
2016-05-23T01:08:48.673636+00:00 app[web.1]: error: Error: API key ID and secret is required.
2016-05-23T01:08:48.673657+00:00 app[web.1]: at newError (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:15:14)
2016-05-23T01:08:48.673659+00:00 app[web.1]: at ValidateClientConfigStrategy.process (/app/node_modules/stormpath-config/lib/strategy/ValidateClientConfigStrategy.js:33:12)
2016-05-23T01:08:48.673660+00:00 app[web.1]: at fn (/app/node_modules/async/lib/async.js:746:34)
2016-05-23T01:08:48.673660+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:1213:16
2016-05-23T01:08:48.673661+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:166:37
2016-05-23T01:08:48.673665+00:00 app[web.1]: at tryOnImmediate (timers.js:534:15)
2016-05-23T01:08:48.673661+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:706:43
2016-05-23T01:08:48.673666+00:00 app[web.1]: at processImmediate [as _immediateCallback] (timers.js:514:5)
2016-05-23T01:08:48.673662+00:00 app[web.1]: at /app/node_modules/async/lib/async.js:167:37
2016-05-23T01:08:48.673664+00:00 app[web.1]: at Immediate._onImmediate (/app/node_modules/async/lib/async.js:1206:34)
2016-05-23T01:09:44.945559+00:00 app[web.1]: Error waiting for process to terminate: No child processes
2016-05-23T01:09:44.916097+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-05-23T01:09:44.916097+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-05-23T01:09:45.800059+00:00 heroku[web.1]: Process exited with status 22
2016-05-23T01:09:45.849441+00:00 heroku[web.1]: State changed from starting to crashed
2016-05-23T01:17:24.998834+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=workpls.herokuapp.com request_id=f573e1ab-6029-4115-b925-3034b93ca7dc fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:17:25.895402+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=workpls.herokuapp.com request_id=eca422af-0a7c-4d10-9bd6-16fc54b6b10d fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:21:00.461372+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=workpls.herokuapp.com request_id=89189a45-6415-48e4-be08-0fb2a83291e8 fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
2016-05-23T01:21:01.050242+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=workpls.herokuapp.com request_id=6d4fa6d5-1feb-4a10-8864-ef50fe72845b fwd="73.222.253.89" dyno= connect= service= status=503 bytes=
I work at Stormpath, so just hopping in here. We recently released a new version of our express-stormpath library, which looks for environment variables with different names than those which are included by default on Heroku.
I'm going to fix this in the Heroku documentation right now.
What you can do to get things working in the interim is this:
$ heroku config:set STORMPATH_APPLICATION_HREF=$(heroku config:get STORMPATH_URL)
$ heroku config:set STORMPATH_CLIENT_APIKEY_ID=$(heroku config:get STORMPATH_API_KEY_ID)
$ heroku config:set STORMPATH_CLIENT_APIKEY_SECRET=$(heroku config:get STORMPATH_API_KEY_SECRET)
Those above commands will duplicate your Heroku environment variables for Stormpath, naming them correctly.
Sorry for the confusion, I'm working on getting this fixed right now =)
I'm using ember-cli and an express as server(is not a mock), what steps
should I do ? I tried the ember-cli but it does not include express...also I connected with github, my logs are:
2015-03-08T02:38:29.848078+00:00 heroku[api]: Deploy b868570 by xxx#gmail.com
2015-03-08T02:38:29.848078+00:00 heroku[api]: Release v6 created by xxx#gmail.com
2015-03-08T02:38:30.082787+00:00 heroku[web.1]: State changed from crashed to starting
2015-03-08T02:38:37.353932+00:00 heroku[web.1]: Starting process with command `sh boot.sh`
2015-03-08T02:38:39.134915+00:00 app[web.1]: nginx: [emerg] "server" directive is not allowed here in /app/config/nginx.conf:4
2015-03-08T02:38:39.961113+00:00 heroku[web.1]: Process exited with status 1
2015-03-08T02:38:39.981607+00:00 heroku[web.1]: State changed from starting to crashed
2015-03-08T02:38:52.513415+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=conne.herokuapp.com request_id=ce29d7bf-2d26-4ead-ad4f-f8037d924410 fwd="177.129.71.147" dyno= connect= service= status=503 bytes=
2015-03-08T02:38:53.349045+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=conne.herokuapp.com request_id=2d98de70-f07e-473d-bb8e-e936b166b33e fwd="177.129.71.147" dyno= connect= service= status=503 bytes=