# Logstash binding problems
**URL:** https://discuss.elastic.co/t/logstash-binding-problems/146410
**Category:** Logstash
**Created:** [August 28, 2018, 6:14pm UTC](https://discuss.elastic.co/t/logstash-binding-problems/146410 "2018-08-28T18:14:33Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@temp44](https://discuss.elastic.co/u/temp44)
#### Post date: [August 28, 2018, 6:14pm UTC](https://discuss.elastic.co/t/logstash-binding-problems/146410/1 "2018-08-28T18:14:33Z")
I am having an issue when running Logstash. When I run it with systemctl, it does not bind on port 5044 at all but logstash is not failing to run. When I run "logstash -f /etc/logstash/conf.d/" it binds to port 5044, but I cannot telnet to it from my other system running beats. I have checked and it is not a firewall issue. The one thing that stands out is that on the output of netstat it shows most other things binding on 127.0.0.1:9300 but for Logstash its :::5044. Any ideas?
Netstat output:
netstat -pltn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 10.144.44.156:5601 0.0.0.0:\* LISTEN 6844/node
tcp 0 0 0.0.0.0:22 0.0.0.0:\* LISTEN 1079/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:\* LISTEN 1355/master
tcp6 0 0 127.0.0.1:9600 :::\* LISTEN 7210/java
tcp6 0 0 10.144.44.156:9200 :::\* LISTEN 6769/java
tcp6 0 0 127.0.0.1:9200 :::\* LISTEN 6769/java
tcp6 0 0 :::5044 :::\* LISTEN 7210/java
tcp6 0 0 10.144.44.156:9300 :::\* LISTEN 6769/java
tcp6 0 0 127.0.0.1:9300 :::\* LISTEN
I'm using a bare bones config to test the bind at the moment so it looks like this:
input {
beats {
port =\> 5044
}
}
output {
elasticsearch {
hosts =\> ["[http://localhost:9200](http://localhost:9200)"]
}
}
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [August 28, 2018, 6:32pm UTC](https://discuss.elastic.co/t/logstash-binding-problems/146410/2 "2018-08-28T18:32:50Z")
It looks like it's only listening on the IPv6 interface. What happens if you set the beats input's `host` option to your IPv4 address? Have you seen [Logstash only listens on IPv6 port](https://discuss.elastic.co/t/logstash-only-listens-on-ipv6-port/57507)?
---
### Author:  [@temp44](https://discuss.elastic.co/u/temp44)
#### Post date: [August 29, 2018, 8:20am UTC](https://discuss.elastic.co/t/logstash-binding-problems/146410/3 "2018-08-29T08:20:18Z")
It was an iptables issue, sorry to waste your time. I knew the main firewall configurations wouldn't have been changed but it seems that port 5044 was removed/not committed on restart maybe. For anyone else with this problem - double check your firewall!
In the end I didn't need to specify anything for the host option, it listened on IPv6 only and worked fine.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 26, 2018, 8:20am UTC](https://discuss.elastic.co/t/logstash-binding-problems/146410/4 "2018-09-26T08:20:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.