# Elasticsearch listen on ipv4 but logstash won't?

**URL:** <https://discuss.elastic.co/t/elasticsearch-listen-on-ipv4-but-logstash-wont/136475>\
**Category:** Logstash\
**Created:** [June 19, 2018, 10:57am UTC](https://discuss.elastic.co/t/elasticsearch-listen-on-ipv4-but-logstash-wont/136475 "2018-06-19T10:57:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![markdaku](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@markdaku](https://discuss.elastic.co/u/markdaku)\
**Post date:** [June 19, 2018, 10:57am UTC](https://discuss.elastic.co/t/elasticsearch-listen-on-ipv4-but-logstash-wont/136475/1 "2018-06-19T10:57:59Z")

</div>

This topic has been tossed around several times.

Both Elasticsearch and Logstash are Java apps. Why is that elastic search can listen on ipv4 out of the box and logstash listens to ipv6 on the same host?

Every single time I have to neuter ipv6 on a host just to let logstash listen on ipv4.

I do not buy the argument that this is how java works. Simply because we have an app, elasticsearch that somehow out of the box can.

At least put into the logstash configuration a commented out configuration that allows for  
ipv4+ipv6, or ipv4, or ipv6

Why does every admin have to dig through mountains of forums to discover this tiny little tidbit of truth buried under mountains of people presenting theories and trial and error. MAKE THIS A DOCUMENTED THING PLEASE. Either in the config or in the installation instructions on the site.

---

<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:** [July 17, 2018, 10:58am UTC](https://discuss.elastic.co/t/elasticsearch-listen-on-ipv4-but-logstash-wont/136475/2 "2018-07-17T10:58:47Z")

</div>

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