# Single node elasticsearch installation with podman and IPv6

**URL:** https://discuss.elastic.co/t/single-node-elasticsearch-installation-with-podman-and-ipv6/351086
**Category:** Elasticsearch
**Tags:** docker
**Created:** [January 15, 2024, 4:20pm UTC](https://discuss.elastic.co/t/single-node-elasticsearch-installation-with-podman-and-ipv6/351086 "2024-01-15T16:20:30Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![hitchalon](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@hitchalon](https://discuss.elastic.co/u/hitchalon)
#### Post date: [January 15, 2024, 4:20pm UTC](https://discuss.elastic.co/t/single-node-elasticsearch-installation-with-podman-and-ipv6/351086/1 "2024-01-15T16:20:30Z")

</div>

Hi all,

I am trying to install Elasticsearch by using podman on a IPv6 only host (RHEL 9.3, podman 4.6.3).

Here is my run commands for elasticsearch and kibana

```auto
podman run --name es01 --net elastic-v6 -p [1000:1400:2400::1]:9200:9200 -e http.publish_host=palantir.middle.earth -e network.host=_global:ipv6_ -it -m 4GB docker.elastic.co/elasticsearch/elasticsearch:8.11.4

podman run --name kib01 --net elastic-v6 -e SERVER_HOST=:: -p [1000:1400:2400::1]:5601:5601 docker.elastic.co/kibana/kibana:8.11.4

```

1000:1400:2400::1 is my host's ipv6 address

With this settings, kibana token brings the host's ip in "Configure Elastic" screen but when I press Configure Elastic button it fails and I get

```auto
Hostname/IP does not match certificate's altnames: IP: 1000:1400:2400::1 is not in the cert's list

```

error in Kibana logs.

If I use the following command to start Elastic pod

```auto
podman run --name es01 --net elastic-v6 -p [1000:1400:2400::1]:9200:9200 -e network.host=_global:ipv6_ -it -m 4GB docker.elastic.co/elasticsearch/elasticsearch:8.11.4
es01

```

This time the token brings the elastic container's ipv6 address and I can succesfully configure and login to Elasticsearch. But when the containers are restarted Kibana still tries to connect by using the previous IP and everything fails.

I tried several combinations of network|http.host|bind\_host|publish\_host settings but couldn't find the correct one.

Any help is much appreciated.

---

<div class="post-metadata">

### Author: ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)
#### Post date: [January 15, 2024, 4:53pm UTC](https://discuss.elastic.co/t/single-node-elasticsearch-installation-with-podman-and-ipv6/351086/2 "2024-01-15T16:53:12Z")

</div>

Hi,

have you tried to update the Elasticsearch SSL certificate to include the IP address `1000:1400:2400::1` in the SAN field? You'll need to generate a new certificate, replace the existing one, and restart Elasticsearch

Regards

---

<div class="post-metadata">

### Author: ![hitchalon](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@hitchalon](https://discuss.elastic.co/u/hitchalon)
#### Post date: [January 16, 2024, 8:40am UTC](https://discuss.elastic.co/t/single-node-elasticsearch-installation-with-podman-and-ipv6/351086/3 "2024-01-16T08:40:02Z")

</div>

Thanks @yago82, I thought about that but I was wondering if one of the parameters injects the node hostname to the certificate automatically. Worst case I will do as you mentioned.

Rgrds,

---

<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: [February 13, 2024, 8:40am UTC](https://discuss.elastic.co/t/single-node-elasticsearch-installation-with-podman-and-ipv6/351086/4 "2024-02-13T08:40:13Z")

</div>

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