Authorization errors trying to connect Kibana 4.1.2 to ES 1.5.2


(Shane Witbeck) #1

I'm struggling to get Kibana (kibana-4.1.2-darwin-x64) to connect to ES 1.5.2 on the same machine. I'm using default configuration for both. I need to stick with ES 1.5.2 but I'm flexible with the version of Kibana. When I run bin/kibana I get the following errors then Kibana stops:

{
  "name": "Kibana",
  "hostname": "APNKG3QPC48112",
  "pid": 31975,
  "level": 50,
  "err": {
    "message": "Authorization Exception",
    "name": "Error",
    "stack": "Error: Authorization Exception\n    at respond (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/transport.js:235:15)\n    at checkRespForFailure (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/transport.js:203:7)\n    at HttpConnector.<anonymous> (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n    at IncomingMessage.bound (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/node_modules/lodash-node/modern/internals/baseBind.js:56:17)\n    at IncomingMessage.emit (events.js:117:20)\n    at _stream_readable.js:944:16\n    at process._tickCallback (node.js:442:13)"
  },
  "msg": "",
  "time": "2015-11-16T16:44:43.290Z",
  "v": 0
}
{
  "name": "Kibana",
  "hostname": "APNKG3QPC48112",
  "pid": 31975,
  "level": 60,
  "err": {
    "message": "Authorization Exception",
    "name": "Error",
    "stack": "Error: Authorization Exception\n    at respond (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/transport.js:235:15)\n    at checkRespForFailure (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/transport.js:203:7)\n    at HttpConnector.<anonymous> (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n    at IncomingMessage.bound (/Users/switbe/tools/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/node_modules/lodash-node/modern/internals/baseBind.js:56:17)\n    at IncomingMessage.emit (events.js:117:20)\n    at _stream_readable.js:944:16\n    at process._tickCallback (node.js:442:13)"
  },
  "msg": "",
  "time": "2015-11-16T16:44:43.291Z",
  "v": 0
}

(Magnus Bäck) #2

It looks like your Elasticsearch requires authentication but you haven't configured Kibana to provide any credentials. Or they're insufficient.


(Shane Witbeck) #3

Thanks for the reply. I've got it working locally but running into the same issue when connecting through a proxy to AWS Elasticsearch. The proxy I'm using is referenced here: https://forums.aws.amazon.com/thread.jspa?threadID=218214

I can use curl to hit the AWS ES REST api but Kibana fails.

Do you have any guidance here?


(Magnus Bäck) #4

I'd use Wireshark to compare Kibana's HTTP requests to curl's.


(Dan) #5

Hi Shane,

Did you ever get this working? I'm running into what seems to be the same issue--I've used that node server to proxy requests to an amazon elastic search cluster, and can run curl commands but not kibana.

Thanks,
Dan


(Shane Witbeck) #6

Yes. You should be able to connect to the AWS ES Kibana plugin once you start the proxy. One thing that bit me is that you need to make sure to include the trailing slash. So /_plugin/kibana/ not /_plugin/kibana.

I don't remember if I got a local instance of Kibana working with AWS ES but if you're attempting that be sure to update the Kibana configuration as explained here: http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-managedomains.html#es-managedomains-kibana

HTH,
Shane


(system) #7