Kibana IPV6 "No living Connections"

[gbahezre]

Kibana version:
Docker 6.4.1 oss

Elasticsearch version:
Docker 6.4.1 oss

Server OS version:
Redhat 7.3

Browser version:
Chrome Version 69.0.3497.100 (Official Build) (64-bit)
Firefox Quantum 62.0.3 (64-bit)

Browser OS version:
Windows 7
Windows 10

Original install method (e.g. download page, yum, from source, etc.):
Docker

Describe the bug:
ELK are all running in docker containers at the latest stable version (6.4.1 oss) using network host configuration.

The configuration is working well in IPV4, but not in IPV6.
Logstash and Kibana are working well both in IPV4 and IPV6.

Kibana Status is OK.

Kibana is able to get all his configuration, visualizations and dashboard from Elastic. I can also use dev tools to launch a custom request to Elastic from Kibana without any problems.

But Kibana Discover, Visualise and Dashboard produce errors like :

Discover: No Living connections

Error: No Living connections
ErrorAbstract@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:817631
NoConnections@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:818107
sendReqWithConnection@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:833303
next@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:840599
Item.prototype.run@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:816138
drainQueue@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:815700

There is no error in any logs (Elastic and Kibana).

Expected behavior:
No error, or explicit error in status or logs at least.

Screenshots (if relevant):

Errors in browser console (if relevant):

ERROR: 2018-10-15T13:53:40Z
Log.prototype.error@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:823935
checkRespForFailure@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:833778
AngularConnector.prototype.request/<@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:189:843294
processQueue@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:104:199684
scheduleProcessQueue/<@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:104:200647
$digest@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:104:210409
$evalAsync/<@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:104:212930
completeOutstandingRequest@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:104:64421
Browser/self.defer/timeoutId<@http://[2a00:8a00:4000:6049::7b]:5601/bundles/vendors.bundle.js:104:67265

vendors.bundle.js:205:74081
WARNING: 2018-10-15T13:53:40Z
Unable to revive connection: http://2a00:8a00:4000:6049::7b:5601/elasticsearch

vendors.bundle.js:205:74081
WARNING: 2018-10-15T13:53:40Z
No living connections

Provide logs and/or server output (if relevant):
There is no error in any logs (Elastic and Kibana).

Any additional context:

Kibana config :

server.host: "::0"
elasticsearch.url: "http://[::1]:9200"
elasticsearch.preserveHost: true

Elastic config :

network.host: ["local","eth1"]
discovery.zen.ping.unicast.hosts: ["xxx-0","xxx-1","xxx-2"]
discovery.zen.minimum_master_nodes: 2
discovery.zen.fd.ping_timeout: 10s

Thanks for your help !

[bhavyarm]

pinging @elastic/kibana-operations

[gbahezre]

Just removed the part concerning Reverse Proxy, as in fact the error is the same when connecting directly to Kibana without Reverse Proxy.

So this is only Basic IPV6 configuration now.

[hhoover]

Square brackets need to be put around this.host in optimize/bundles/vendors.bundle.js for IPv6 to work, as it builds the ElasticSearch URL using an IP address without brackets and the URL is broken. I'm not positive how this URL is built (I think it's in core_plugins/elasticsearch/lib/parse_config.js).

[gbahezre]

This is exactly the problem.
In fact, connection between Kibana and ElasticSearch is working fine, Kibana status is OK and Kibana is able to get his index from ElasticSearch.

The only thing that does not work is getting index values from browser (requesting ElasticSearch throught Kibana from browser).
For example : https://[IPV6]:5601/elasticsearch/_msearch

I tried your fix but it doesn't work, it applies for all connections, not only this one, making other connections to ElasticSearch to fail.

I fix it by patching file "optimize/bundles/vendors.bundle.js" in function "Host.prototype.makeUrl" by adding brackets around host.
I think this can be done also in "ConnectionPool.prototype.setHosts" function.

This is only a workaround, because this will not work for IPV4. But for now i didn't find exactly from where host parameters are comming from.

Thanks @hhoover ! You help me find out what was exactly the problem, i was looking for it for quite a long time now :)

[ysundar]

When this will be fixed.