I deployed this app on Heroku for the first time 6 months ago and it was running fine. Its still running fine on localhost but now when I try to use the same heroku link its showing application error.
Here are my logs:
heroku logs --tail
2021-11-22T21:25:37.247493+00:00 heroku[web.1]: Restarting
2021-11-22T21:25:37.291674+00:00 heroku[web.1]: State changed from up to starting
2021-11-22T21:25:38.213115+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2021-11-22T21:25:38.434284+00:00 heroku[web.1]: Process exited with status 143
2021-11-22T21:25:39.432521+00:00 heroku[web.1]: Starting process with command `node app.js`
2021-11-22T21:25:40.721334+00:00 app[web.1]: Database_URL undefined
2021-11-22T21:25:40.722187+00:00 app[web.1]: Server has started
2021-11-22T21:25:41.145424+00:00 heroku[web.1]: State changed from starting to up
2021-11-22T21:26:10.715356+00:00 app[web.1]: connect ECONNREFUSED 127.0.0.1:27017
2021-11-22T21:26:20.762822+00:00 heroku[router]: at=info method=GET path="/" host=sleepy-basin-23202.herokuapp.com request_id=9145c837-b0b8-409e-af04-38431cef02a5 fwd="47.15.8.93" dyno=web.1 connect=0ms service=12ms status=304 bytes=151 protocol=https
2021-11-22T21:26:21.119967+00:00 heroku[router]: at=info method=GET path="/style.css" host=sleepy-basin-23202.herokuapp.com request_id=7cd5ff7a-a627-4f97-a28f-b4f73b08b463
fwd="47.15.8.93" dyno=web.1 connect=0ms service=9ms status=200 bytes=4543 protocol=https
2021-11-22T21:26:21.123105+00:00 heroku[router]: at=info method=GET path="/script.js" host=sleepy-basin-23202.herokuapp.com request_id=3176b0d8-80b4-4c6c-a389-cc786bbd0e0f
fwd="47.15.8.93" dyno=web.1 connect=0ms service=7ms status=404 bytes=392 protocol=https
2021-11-22T21:26:21.452457+00:00 heroku[router]: at=info method=GET path="/script.js" host=sleepy-basin-23202.herokuapp.com request_id=cbdc660f-90e1-443b-8b2d-2f255018b63d
fwd="47.15.8.93" dyno=web.1 connect=0ms service=2ms status=404 bytes=392 protocol=https
2021-11-22T21:26:22.904249+00:00 heroku[router]: at=info method=POST path="/view" host=sleepy-basin-23202.herokuapp.com request_id=3a4c38b1-5798-490e-bc1b-73338fc18cf5 fwd="47.15.8.93" dyno=web.1 connect=0ms service=13ms status=302 bytes=246 protocol=https
2021-11-22T21:26:33.202949+00:00 app[web.1]: (node:4) UnhandledPromiseRejectionWarning: MongooseError: Operation `users.find()` buffering timed out after 10000ms
2021-11-22T21:26:33.202957+00:00 app[web.1]: at Timeout.<anonymous> (/app/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185:20)
2021-11-22T21:26:33.202958+00:00 app[web.1]: at listOnTimeout (internal/timers.js:554:17)
2021-11-22T21:26:33.202959+00:00 app[web.1]: at processTimers (internal/timers.js:497:7)
2021-11-22T21:26:33.202960+00:00 app[web.1]: (Use `node --trace-warnings ...` to show where the warning was created)
2021-11-22T21:26:33.203001+00:00 app[web.1]: (node:4) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
2021-11-22T21:26:33.203100+00:00 app[web.1]: (node:4) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are
not handled will terminate the Node.js process with a non-zero exit code.
2021-11-22T21:26:53.190725+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/view" host=sleepy-basin-23202.herokuapp.com request_id=23595d4a-6e69-48cf-a1ce-2ef12ce13815 fwd="47.15.8.93" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0 protocol=https
There isn't much information here, but I see
Database_URL undefined
in your logs. Assuming you are using a Heroku database addon like Heroku Postgres, your database URL will be defined in a variable called DATABASE_URL. Case is important: DATABASE_URL and Database_URL are different things.
Please update your code to use DATABASE_URL.
Note that environment variable names are not case-sensitive on Windows. If you are using Windows for local development that's one reason this might work locally and not work on Heroku.
It can't find you database Url check your env configuration
Related
I was trying to deploy my dashboard on heroku but after I finished I got Request timeout error
I got an Application error and search a lot but still have the same problem of time out and quota memory exceeded
Here is the error from the activity log:
2022-05-02T19:12:39.725777+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=ukraineinvasion.herokuapp.com request_id=fc485f9
6-0c39-416e-914a-93a3c9e1b6e8 fwd="41.46.189.30" dyno=web.1 connect=0ms service=30004ms status=503 bytes=0 protocol=https
2022-05-02T19:12:40.714784+00:00 app[web.1]: Dash is running on http://127.0.0.1:59351/
This might be a stupid question to ask but are there any extra steps I need to complete to deploy a phoenix liveview app to heroku?
From official documents deployment of phoenix app was successful but converting the same page into a liveview caused the page to reload infinitely
And the error I get on heroku logs are:
2022-01-18T07:35:12.424013+00:00 heroku[router]: at=info method=GET path="/" host=fast-fortress-60216.herokuapp.com request_id=0bf752c3-185a-44d4-84ce-7004f7031984 fwd="27.34.20.173" dyno=web.1 connect=0ms service=2ms status=200 bytes=4941 protocol=https
2022-01-18T07:35:13.895958+00:00 heroku[router]: at=info method=GET path="/assets/app-097a5c6ca9e10ff4881312b83e54a14f.css?vsn=d" host=fast-fortress-60216.herokuapp.com request_id=8d4e402d-cf16-4e4d-8b26-3bdcbbc6186c fwd="27.34.20.173" dyno=web.1 connect=0ms service=2ms status=200 bytes=15612 protocol=https
2022-01-18T07:35:15.191409+00:00 heroku[router]: at=info method=GET path="/live/websocket?_csrf_token=SC9hAXBiKRoOLDYALRkhCT8EBzk8LT0syDSs70xHbMfQfZyowhVUrjDs&_track_static%5B0%5D=https%3A%2F%2Ffast-fortress-60216.herokuapp.com%2Fassets%2Fapp-097a5c6ca9e10ff4881312b83e54a14f.css%3Fvsn%3Dd&_track_static%5B1%5D=https%3A%2F%2Ffast-fortress-60216.herokuapp.com%2Fassets%2Fapp-a670ca05a10bcaada1c4842b40be19a2.js%3Fvsn%3Dd&_mounts=0&vsn=2.0.0" host=fast-fortress-60216.herokuapp.com request_id=e8ef08c8-d80a-4a79-8b73-d21cc5e47d2c fwd="27.34.20.173" dyno=web.1 connect=0ms service=1ms status=403 bytes=195 protocol=https
2022-01-18T07:35:15.191230+00:00 app[web.1]: 07:35:15.191 [error] Could not check origin for Phoenix.Socket transport.
2022-01-18T07:35:15.191243+00:00 app[web.1]:
2022-01-18T07:35:15.191244+00:00 app[web.1]: Origin of the request: https://fast-fortress-60216.herokuapp.com
2022-01-18T07:35:15.191244+00:00 app[web.1]:
2022-01-18T07:35:15.191245+00:00 app[web.1]: This happens when you are attempting a socket connection to
2022-01-18T07:35:15.191246+00:00 app[web.1]: a different host than the one configured in your config/
2022-01-18T07:35:15.191246+00:00 app[web.1]: files. For example, in development the host is configured
2022-01-18T07:35:15.191246+00:00 app[web.1]: to "localhost" but you may be trying to access it from
2022-01-18T07:35:15.191247+00:00 app[web.1]: "127.0.0.1". To fix this issue, you may either:
2022-01-18T07:35:15.191247+00:00 app[web.1]:
2022-01-18T07:35:15.191248+00:00 app[web.1]: 1. update [url: [host: ...]] to your actual host in the
2022-01-18T07:35:15.191248+00:00 app[web.1]: config file for your current environment (recommended)
2022-01-18T07:35:15.191248+00:00 app[web.1]:
2022-01-18T07:35:15.191248+00:00 app[web.1]: 2. pass the :check_origin option when configuring your
2022-01-18T07:35:15.191249+00:00 app[web.1]: endpoint or when configuring the transport in your
2022-01-18T07:35:15.191249+00:00 app[web.1]: UserSocket module, explicitly outlining which origins
2022-01-18T07:35:15.191250+00:00 app[web.1]: are allowed:
2022-01-18T07:35:15.191251+00:00 app[web.1]:
2022-01-18T07:35:15.191251+00:00 app[web.1]: check_origin: ["https://example.com",
2022-01-18T07:35:15.191251+00:00 app[web.1]: "//another.com:888", "//other.com"]
Do I have to install extra buildpacks or some changes in my configs?
My bad
The solution was right there but I didn't exactly know how to implement it.
The solution is adding
config :grasruts, GrasrutsWeb.Endpoint, check_origin: ["http://localhost:4000/","https://HEROKU_APP_URL/"]
I have a problem with deploying Strapi application on Heroku. Both local and Heroku Strapi setups are using Postgres database.
Can't see any errors in Heroku logs, just a blank page in browser. Brpwser's console has these two errors:
Uncaught SyntaxError: Unexpected token '<' runtime~main.8073a043.js:1
Uncaught SyntaxError: Unexpected token '<' main.abbe0ac9.chunk.js:1
Heroku logs:
2020-12-11T15:26:03.986177+00:00 heroku[web.1]: State changed from starting to up
2020-12-11T15:26:03.916838+00:00 app[web.1]: INFO: Accepting connections at http://localhost:58777
2020-12-11T15:26:04.470749+00:00 heroku[router]: at=info method=GET path="/" host=john-strapi-postgres.herokuapp.com request_id=8783501f-3d9f-4986-bb44-6648a93d8105 fwd="68.82.27.99" dyno=web.1 connect=1ms service=24ms status=304 bytes=85 protocol=https
2020-12-11T15:26:04.561029+00:00 heroku[router]: at=info method=GET path="/admin/runtime~main.8073a043.js" host=john-strapi-postgres.herokuapp.com request_id=008157f5-a2ff-4738-9a8c-8ef4ac76a2d8 fwd="68.82.27.99" dyno=web.1 connect=1ms service=3ms status=304 bytes=85 protocol=https
2020-12-11T15:26:04.558537+00:00 heroku[router]: at=info method=GET path="/admin/main.abbe0ac9.chunk.js" host=john-strapi-postgres.herokuapp.com request_id=aa2e15a8-e001-4333-a195-f669ddcaac74 fwd="68.82.27.99" dyno=web.1 connect=1ms service=5ms status=304 bytes=85 protocol=https
2020-12-11T15:26:04.666249+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=john-strapi-postgres.herokuapp.com request_id=f2342dac-0347-4b0b-a4e4-89f0a425a98a fwd="68.82.27.99" dyno=web.1 connect=0ms service=6ms status=304 bytes=85 protocol=https
Local Strapi application runs perfectly fine.
Node v. 14.5.1
NPM v. 6.14.8
Strapi v. 3.3.4
Windows 10
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 =)
After pushing on heroku my #Messages(value) are not interpreted:
--> value is display instead of the translation present in conf/Messages file.
I use play framework 2.2.1.
Here is the log of a start and a first display of a page containning #Messsages() use.
2014-10-12T05:37:14.320052+00:00 heroku[web.1]: State changed from down to starting
2014-10-12T05:37:14.320052+00:00 heroku[web.1]: Unidling
2014-10-12T05:37:24.363328+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/kosh -Dhttp.port=41328 -DapplyEvolutions.default=true`
2014-10-12T05:37:25.260260+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Djava.rmi.server.useCodebaseOnly=true
2014-10-12T05:37:25.672105+00:00 app[web.1]: Play server process ID is 2
2014-10-12T05:37:27.084724+00:00 app[web.1]: [←[37minfo←[0m] play - database [default] connected at jdbc:h2:mem:play
2014-10-12T05:37:27.660047+00:00 app[web.1]: [←[37minfo←[0m] play - Application started (Prod)
2014-10-12T06:39:14.765169+00:00 heroku[router]: at=info method=GET path="/" host=mmmm.herokuapp.com request_id=31eeed7d-0b4d-43ac-b2df-3d142f6db4ba fwd="-" dyno=web.1 connect=1ms service=16ms status=200 bytes=34657
2014-10-12T06:39:14.939740+00:00 heroku[router]: at=info method=GET path="/assets/stylesheets/bootstrap.min.css" host=mmmm.herokuapp.com request_id=7ffe7b15-d521-481fb9f1-fba1c146fbf0 fwd="-" dyno=web.1 connect=1ms service=7ms status=304 bytes=173
2014-10-12T06:39:14.949590+00:00 heroku[router]: at=info method=GET path="/assets/stylesheets/normalize.css" host=mmmm.herokuapp.com request_id=4616036b-d3d3-4891-bc69-8c3461d69e26 fwd="-" dyno=web.1 connect=1ms service=8ms status=304 bytes=1732
2014-10-12T06:47:05.367842+00:00 heroku[router]: at=info method=GET path="/webjars/jquery/1.9.1/jquery.min.js" host=mmmm.herokuapp.com request_id=2938c0d1-62ad-4e43-acdb-1dc23588754f fwd="-" dyno=web.1 connect=1ms service=5ms status=304 bytes=173
My Procfile contains :
web: target/universal/stage/bin/kosh -Dhttp.port=$PORT -DapplyEvolutions.default=true
Changing the name of the file from "Messages" to "messages" (with a lowercase m) had fix the problem. On my Windows side file was case insensitive, on heroku side, in an Unix world, file names were case sensitives. Play framework seem to look for file in lower case at heroku.