# Logstash unable to collect logs from filebeat due to protocol mismatch

**URL:** <https://discuss.elastic.co/t/logstash-unable-to-collect-logs-from-filebeat-due-to-protocol-mismatch/335269>\
**Category:** Logstash\
**Created:** [June 6, 2023, 5:18am UTC](https://discuss.elastic.co/t/logstash-unable-to-collect-logs-from-filebeat-due-to-protocol-mismatch/335269 "2023-06-06T05:18:07Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [June 6, 2023, 10:18am UTC](https://discuss.elastic.co/t/logstash-unable-to-collect-logs-from-filebeat-due-to-protocol-mismatch/335269/4 "2023-06-06T10:18:50Z")

</div>

Ah ok, if there's a reason you're using Filebeat I don't want to mess with that.

> [@Chel\_Db](#):
>
> ssl =\> false

I see you have ssl set to false. Is there a reason for that? Could this be a SSL/TLS settings mismatch? I did also find [a thread using Elastic Agent rather than Beats](https://discuss.elastic.co/t/fleet-agent-logstash-output-invalid-version-of-beats-protocol/314624) where there was a misconfiguration of the TLS settings.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-unable-to-collect-logs-from-filebeat-due-to-protocol-mismatch/335269)._