# Elasticsearch does not listen on ipv4

**URL:** https://discuss.elastic.co/t/elasticsearch-does-not-listen-on-ipv4/300748
**Category:** Elasticsearch
**Created:** [March 26, 2022, 9:04am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-listen-on-ipv4/300748 "2022-03-26T09:04:59Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![sharbich](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@sharbich](https://discuss.elastic.co/u/sharbich)
#### Post date: [March 26, 2022, 9:04am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-listen-on-ipv4/300748/1 "2022-03-26T09:04:59Z")

</div>

Hello, my dears,  
I installed Elasticsearch on my Debian Buster Server. The following ports have been opened.

```auto
root@dsme01:~# netstat -tulpen | grep 192.168.150.20
tcp6 0 0 192.168.150.20:9200 :::* LISTEN 137 487760242 19429/java          
tcp6 0 0 192.168.150.20:9300 :::* LISTEN 137 487760026 19429/java  

```

I notice that only ipv6 connections are displayed. Why?  
My elsaticsearch.yml looks like this

```auto
root@dsme01:~# cat /etc/elasticsearch/elasticsearch.yml 
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: elasticsearch.intern.example.com
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
cluster.initial_master_nodes: ["dsme01"]
http.host: elasticsearch.intern.example.com
transport.host: elasticsearch.intern.example.com
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch

```

What am I doing wrong?

Greetings from Stefan Harbich

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 26, 2022, 10:15am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-listen-on-ipv4/300748/2 "2022-03-26T10:15:34Z")

</div>

Are you referring to the `tcp6` in the netstat output? That's normal, or at least not unexpected in certain configs, and doesn't indicate a problem. There's some sort of compatibility layer in play that makes these sockets appear to be using IPv6 but the addresses are IPv4 addresses and that's what really matters.

---

<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: [April 23, 2022, 10:16am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-listen-on-ipv4/300748/3 "2022-04-23T10:16:09Z")

</div>

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