# Beats not able to connect with Logstash

**URL:** <https://discuss.elastic.co/t/beats-not-able-to-connect-with-logstash/273093>\
**Category:** Logstash\
**Created:** [May 15, 2021, 9:21pm UTC](https://discuss.elastic.co/t/beats-not-able-to-connect-with-logstash/273093 "2021-05-15T21:21:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![robinhood\_lko](https://avatars.discourse-cdn.com/v4/letter/r/5f8ce5/32.png) [@robinhood\_lko](https://discuss.elastic.co/u/robinhood_lko)\
**Post date:** [May 16, 2021, 4:29pm UTC](https://discuss.elastic.co/t/beats-not-able-to-connect-with-logstash/273093/3 "2021-05-16T16:29:09Z")

</div>

Thanks Badger for the quick response. I have tried this solution mentioned here and it worked for me. Thanks a lot for quick help.

> [@Filebeat to Logstash over SSL](https://discuss.elastic.co/t/filebeat-to-logstash-over-ssl/122735/5):
>
> @Ben96 Thank you for your replies. I'm posting this in hopes it helps someone else down the line. After working with our support, the solution is to NOT specify the CA in the pipeline input and to NOT specify the HTTPS protocol in the Filebeat output. Communication to Logstash is not HTTPS (it's some other protocol leftover from Lumberjack) and there's something weird about specifying the CA in the input when it's not needed to authenticate the client. Here's the working config: filebeat.ym…

---

_[View the full topic](https://discuss.elastic.co/t/beats-not-able-to-connect-with-logstash/273093)._