# Filebeat ssl kafka

**URL:** <https://discuss.elastic.co/t/filebeat-ssl-kafka/126923>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 5, 2018, 12:32pm UTC](https://discuss.elastic.co/t/filebeat-ssl-kafka/126923 "2018-04-05T12:32:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajayrc](https://avatars.discourse-cdn.com/v4/letter/a/c77e96/32.png) [@ajayrc](https://discuss.elastic.co/u/ajayrc)\
**Post date:** [April 5, 2018, 12:32pm UTC](https://discuss.elastic.co/t/filebeat-ssl-kafka/126923/1 "2018-04-05T12:32:11Z")

</div>

How to make file beat to send data to kafka via ssl ?

> [@Setting Filebeat 5 with Kafka 0.10 over TLS](https://discuss.elastic.co/t/setting-filebeat-5-with-kafka-0-10-over-tls/59550/3):
>
> When I tried the bash script you provided, which I see just follows the directions on Kafka docs, I got the same error in filebeat. Exiting: error initializing publisher: crypto/tls: failed to parse private key Looking into it I noticed that the script generated DSA keys for the server and client rather than RSA keys. The generated key worked okay from openssl but failed from filebeat. From my tests it looks like filebeat does not support DSA keys and will fail if one is used in either the …

am using the approach told here by anefassa but am getting error  
pipeline/output.go:74 kafka/client.go:69 Kafka connect fails with: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)  
2018-04-05T18:01:25.265+0530 ERROR pipeline/output.go:74 Failed to connect: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)

---

<div class="post-metadata">

**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:** [April 5, 2018, 2:35pm UTC](https://discuss.elastic.co/t/filebeat-ssl-kafka/126923/2 "2018-04-05T14:35:33Z")

</div>

To me the log message indicates that you haven't setup kafka correctly. The log should contain some messages (much earlier in the log), why the beat could not connect. But most likely it is your kafka server configuration not correctly configuring the listeners.

---

<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 3, 2018, 2:35pm UTC](https://discuss.elastic.co/t/filebeat-ssl-kafka/126923/3 "2018-05-03T14:35:50Z")

</div>

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