Dev Tools Console does not appear to work over IPv6 Network Host

[sachin-frayne]

Kibana version: 7.7.1

Elasticsearch version: 7.7.1

Server OS version: MacOS 10.15.4 and Linux 5.6.12-1-MANJARO

Browser version: Chrome MacOS 83.0.4103.61 and Chrome Linux 83.0.4103.97

Browser OS version: MacOS 10.15.4 and Linux 5.6.12-1-MANJARO

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

Description of the problem including expected versus actual behavior: When Connecting Kibana to Elasticseach via an IPv6 IP Address, I expect the Dev Tools Console to work as it does via an IPv4 IP Address, however, this is not the case, I have tried other Kibana Apps and they seem to work fine, including Index Management, Search Profiler and a couple of others.

Steps to reproduce:

1. Start Elasticsearch and bind network.host: "fde1:..." to the systems local IPv6 Address
2. Start Kibana and bind elasticsearch.hosts: ["http://[fde1:...]:9200"] to the same address as above
3. Open Kibana and navigate to the Dev Tools Console, and run any request

Errors in browser console (if relevant):

{"statusCode":502,"error":"Bad Gateway","message":"getaddrinfo ENOTFOUND [fde1:...] [fde1:...]:9200"}

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[jloleysens]

@sachin-frayne Thanks for reporting this! I was able to reproduce and have created a fix that should hopefully be merged soon.