# Logstash listening on tcp6 only

**URL:** <https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026>\
**Category:** Logstash\
**Created:** [April 11, 2017, 5:28pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026 "2017-04-11T17:28:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Drew\_Rogers](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@Drew\_Rogers](https://discuss.elastic.co/u/Drew_Rogers)\
**Post date:** [April 11, 2017, 5:28pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026/1 "2017-04-11T17:28:20Z")

</div>

I upgraded my stack to 5.3.0. I noticed that for all my inputs, logstash is only listening on tcp6 and not tcp4.

For instance my input for beats is:  
 ![](https://us1.discourse-cdn.com/elastic/original/3X/c/e/ced1480c2c5dafbc3137e57e4f2a31cb7fe3a3b7.jpg)

and when logstash starts here are my listening ports:

 ![](https://us1.discourse-cdn.com/elastic/original/3X/0/c/0c46d63778659346142cdfc7b7303b832e12a8f0.png)

---

<div class="post-metadata">

**Author:** ![Drew\_Rogers](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@Drew\_Rogers](https://discuss.elastic.co/u/Drew_Rogers)\
**Post date:** [April 11, 2017, 6:07pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026/2 "2017-04-11T18:07:46Z")

</div>

So I disabled IP6 on my server and rebooted. Now I have logstash listening on 5044 via IP4:

 ![](https://us1.discourse-cdn.com/elastic/original/3X/4/3/4319db457b82b77fba340f165e8373b5284a112e.png)

However I cannot telnet into the logstash server via port 5044 and nmap reports the following opening ports:

 ![](https://us1.discourse-cdn.com/elastic/original/3X/7/9/79b9a8fab67e4e7d6ff1aad048f762f475c1bab5.png)

There is no firewall setup

---

<div class="post-metadata">

**Author:** ![jkuang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkuang/32/72637_2.png) [@jkuang](https://discuss.elastic.co/u/jkuang)\
**Post date:** [April 11, 2017, 6:14pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026/3 "2017-04-11T18:14:40Z")

</div>

Are you just reporting this so other people are aware or are you needing confirmation that IP6 is what it now uses in ES 5.3?

---

<div class="post-metadata">

**Author:** ![Drew\_Rogers](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@Drew\_Rogers](https://discuss.elastic.co/u/Drew_Rogers)\
**Post date:** [April 11, 2017, 6:24pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026/4 "2017-04-11T18:24:56Z")

</div>

I'm reporting because logstash states it's listening on port 5044, but the port is not open, which I'm sure would be an issue to a lot of people with the same problem.

All of my filebeat agents cannot connect to my logstash server anymore due to port not being open, even though Logstash and netstat claims it is.

I moved from version 5 which had no issues, to 5.3.0.

---

<div class="post-metadata">

**Author:** ![jkuang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkuang/32/72637_2.png) [@jkuang](https://discuss.elastic.co/u/jkuang)\
**Post date:** [April 11, 2017, 7:39pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026/5 "2017-04-11T19:39:27Z")

</div>

I have no issues with Logstash 5.3 with IPV6. I check Logstash 5.0 and it is also using IPV6 only. It also works with no problem.

---

<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:** [May 9, 2017, 7:50pm UTC](https://discuss.elastic.co/t/logstash-listening-on-tcp6-only/82026/6 "2017-05-09T19:50:45Z")

</div>

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