Kibana docker image connecting to Elastic without xpack: redirect loop


(Justin Lee) #1

Hi,

I have an Elastic cluster that intentionally doesn't have the xpack plugin installed. It's up and running, and if I use the soon-to-be-deprecated Docker Hub Kibana image (https://hub.docker.com/_/kibana/) to connect to it, everything works perfectly.

Since the Docker Hub Kibana image is being deprecated, I'd like to figure out how to use the "new" elastic.co Kibana image (docker.elastic.co/kibana/kibana:5.4.0). I'm running it like this:

docker run --rm -p 5601:5601 -e SERVER_HOST=0.0.0.0 -e ELASTICSEARCH_URL=http://<hostname>:9200 docker.elastic.co/kibana/kibana:5.4.0

Every time I set it up and try to navigate to it, I get ERR_TOO_MANY_REDIRECTS.

If I try to curl it, I get something similar.

Looking at the logs, I'm getting a bunch of this:

{"type":"log","@timestamp":"2017-05-31T21:13:29Z","tags":["license","warning","xpack"],"pid":1,"message":"License information could not be obtained from Elasticsearch. [illegal_argument_exception] No endpoint or operation is available at [_xpack] :: {\"path\":\"/_xpack\",\"statusCode\":400,\"response\":\"{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"illegal_argument_exception\\\",\\\"reason\\\":\\\"No endpoint or operation is available at [_xpack]\\\"}],\\\"type\\\":\\\"illegal_argument_exception\\\",\\\"reason\\\":\\\"No endpoint or operation is available at [_xpack]\\\"},\\\"status\\\":400}\"}"}
Unhandled rejection [illegal_argument_exception] No endpoint or operation is available at [_xpack] :: {"path":"/_xpack","statusCode":400,"response":"{\"error\":{\"root_cause\":[{\"type\":\"illegal_argument_exception\",\"reason\":\"No endpoint or operation is available at [_xpack]\"}],\"type\":\"illegal_argument_exception\",\"reason\":\"No endpoint or operation is available at [_xpack]\"},\"status\":400}"}
    at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:295:15)
    at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:254:7)
    at HttpConnector.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:157:7)
    at IncomingMessage.bound (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/dist/lodash.js:729:21)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Is the redirect error because I'm trying to connect to Elastic without xpack, or something else? Is there a way to connect the official Kibana image to Elastic without xpack?

Thanks!


(Jon Budzenski) #2

The docker kibana images come with x-pack preinstalled, and it looks like the current workaround is to uninstall it. There's an open issue at https://github.com/elastic/kibana-docker/issues/27#issuecomment-296524205. It has an example dockerfile to remove it.


(Justin Lee) #3

Sorry, should've searched the git repo first. Thanks for the help!


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.