# Kibana and IPv6

**URL:** <https://discuss.elastic.co/t/kibana-and-ipv6/231478>\
**Category:** Kibana\
**Created:** [May 7, 2020, 7:56am UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478 "2020-05-07T07:56:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\
**Post date:** [May 7, 2020, 7:56am UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478/1 "2020-05-07T07:56:23Z")

</div>

There doesn't seem to be any way to consistently configure kibana to listen on both IPv4 and IPv6 addresses of a dual-stack server.  
There are similar open issues which discuss the fact that kibana is parsing the `server.host` parameter as a hostname and thus doesn't accept IPv6 hex addresses, but there are other problems:

1. You can't specify multiple addresses
2. Using `0.0.0.0` doesn't make kibana listen on IPv6
3. The `server.host` parameter is actually used for the redirect uri when using openid connect, so this would redirect the browser to `https://0.0.0.0/...` which is just insane

So there should really be a seperate setting for `listen_address` and `service_name`

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [May 11, 2020, 4:10pm UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478/2 "2020-05-11T16:10:29Z")

</div>

1. That is true and intended.
2. Wouldn't the 0.0.0.0 equivalent for ipv6 be `::/0` ?

You can open an enhancement request for the others here: [https://github.com/elastic/kibana](https://github.com/elastic/kibana)

---

<div class="post-metadata">

**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\
**Post date:** [May 12, 2020, 12:34pm UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478/3 "2020-05-12T12:34:58Z")

</div>

So you need two kibana instances to listen on both IPv4 and IPv6 ?

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [May 12, 2020, 4:08pm UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478/4 "2020-05-12T16:08:05Z")

</div>

Indeed. Or you can listen to localhost and do port forwarding and IPv4/ipv6 translation from the router.

---

<div class="post-metadata">

**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\
**Post date:** [May 20, 2020, 3:45pm UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478/5 "2020-05-20T15:45:33Z")

</div>

This is quite a limitation, IMHO

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 17, 2020, 3:45pm UTC](https://discuss.elastic.co/t/kibana-and-ipv6/231478/6 "2020-06-17T15:45:40Z")

</div>

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