-
Notifications
You must be signed in to change notification settings - Fork 135
Open
Description
After configuring the access policy on aws,
I can access kibana via aws-es-kibana proxy.
But after deploying to heroku, I can see the log message like this:
2017-06-30T09:03:16.344356+00:00 app[web.1]: Kibana available at http://127.0.0.1:50970/_plugin/kibana/
2017-06-30T09:03:16.344258+00:00 app[web.1]: AWS ES cluster available at http://127.0.0.1:50970
But when I access to https://<MY_HEROKUAPP>.herokuapp.com or https://<MY_HEROKUAPP>.herokuapp.com/_plugin/kibana,
Errors suddenly show up:
2017-06-30T09:04:33.967079+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=<MY_HEROKUAPP>.herokuapp.com request_id=7b787b96-d988-4cab-9845-adf89a2d5bf4 fwd="IP" dyno= connect= service= status=503 bytes= protocol=https
2017-06-30T09:04:34.778436+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/_plugin/kibana" host=<MY_HEROKUAPP>.herokuapp.com request_id=2cc7a8ee-e679-47a2-b599-766e9325579c fwd="IP" dyno= connect= service= status=503 bytes= protocol=http
The weird thing is I don't get any other error message,
and the local version went just fine.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels