# Simple test showing that logstash port is reachable by filebeat **URL:** \ **Category:** Beats\ **Created:** [July 20, 2016, 3:01pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999 "2016-07-20T15:01:47Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![zoplex](https://avatars.discourse-cdn.com/v4/letter/z/bc8723/32.png) [@zoplex](https://discuss.elastic.co/u/zoplex)\ **Post date:** [July 20, 2016, 3:01pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999/1 "2016-07-20T15:01:48Z")
We are looking at larger number of filebeats installations in the production environments. One challenge is that in some cases logstash host:5044 is not reachable from the filebeat host. How do we check using curl (nc is not available) that filebeat will be able to talk to logstash? I tried in cases where that connectivity is working fine and curl -v will return 'connection refused'; in cases where it does not have connectivity it would hang - but is there a better way/more definitive? I need to tell users that are installing filebeat a definitive way so we do not even go with the install if the connectivity is not working (opening ports is separate task in a sense that we still need to figure out what exactly is needed to establish that connectivity). Thanks ---
**Author:** ![PhaedrusTheGreek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phaedrusthegreek/32/4884_2.png) [@PhaedrusTheGreek](https://discuss.elastic.co/u/PhaedrusTheGreek)\ **Post date:** [July 20, 2016, 3:11pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999/2 "2016-07-20T15:11:16Z")
@zoplex, If the `telnet` utility is available, that can easily be used to test for an open port. ```auto $ telnet google.ca 443 Trying 172.217.3.131... Connected to google.ca. Escape character is '^]'. Connection closed by foreign host. ``` Let me know if that helps ---
**Author:** ![zoplex](https://avatars.discourse-cdn.com/v4/letter/z/bc8723/32.png) [@zoplex](https://discuss.elastic.co/u/zoplex)\ **Post date:** [July 20, 2016, 4:12pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999/3 "2016-07-20T16:12:44Z")
Yes - that works well - thanks! ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [July 20, 2016, 7:38pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999/4 "2016-07-20T19:38:53Z")
just for checking a tcp port being available I prefer netcat over telnet though (besides telnet client being available mostly on any system): `$ nc -zv `. [Ncat](https://nmap.org/ncat/) is a modern netcat on steroids. ---
**Author:** ![zoplex](https://avatars.discourse-cdn.com/v4/letter/z/bc8723/32.png) [@zoplex](https://discuss.elastic.co/u/zoplex)\ **Post date:** [July 20, 2016, 9:01pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999/5 "2016-07-20T21:01:45Z")
Thank you - we do not have it installed on all VMs so I had to look for different approach - but thanks regardless. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 10, 2016, 3:01pm UTC](https://discuss.elastic.co/t/simple-test-showing-that-logstash-port-is-reachable-by-filebeat/55999/6 "2016-08-10T15:01:53Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.