# Filebeat and logstash ssl config is correct?

**URL:** https://discuss.elastic.co/t/filebeat-and-logstash-ssl-config-is-correct/316868
**Category:** Logstash
**Created:** [October 18, 2022, 9:26am UTC](https://discuss.elastic.co/t/filebeat-and-logstash-ssl-config-is-correct/316868 "2022-10-18T09:26:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Nikolas1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolas1306/32/111507_2.png) [@Nikolas1306](https://discuss.elastic.co/u/Nikolas1306)
#### Post date: [October 18, 2022, 9:26am UTC](https://discuss.elastic.co/t/filebeat-and-logstash-ssl-config-is-correct/316868/1 "2022-10-18T09:26:39Z")

</div>

filebeat

```auto
filebeat.inputs:
- type: filestream
  paths:

        - G:\filebeat-8.4.3-windows-x86_64\logs\*.*
    
output.logstash:
  hosts: ["172.22.10.202:5044"]
  protocol: "http"
  ssl.enabled: true
  ssl.certificate_authorities: ["G:\\logstash-forwarder.crt"]

```

logstash

```auto
input {
    beats {
      host => "172.22.10.202"
      port => 5044
      include_codec_tag => false
      ssl => true
      ssl_certificate => "/etc/ssl/certs/logstash-forwarder.crt"
      ssl_key => "/etc/ssl/private/logstash-forwarder.key"
    }
}

output {

		elasticsearch {
			hosts => ["localhost:9200"]
			index => "fsbroker"
		}
		

		stdout { codec => rubydebug }
}

```

how verify ssl is enable?

---

<div class="post-metadata">

### Author: ![Nikolas1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolas1306/32/111507_2.png) [@Nikolas1306](https://discuss.elastic.co/u/Nikolas1306)
#### Post date: [October 18, 2022, 9:31am UTC](https://discuss.elastic.co/t/filebeat-and-logstash-ssl-config-is-correct/316868/2 "2022-10-18T09:31:23Z")

</div>

i have changed certificate client and in the server have Received _fatal alert: bad\_certificate_  
ok very good is perfect

`````auto
[2022-10-18T09:30:32,193][INFO][org.logstash.beats.BeatsHandler][terza][8fb7acdb9937ab76f029df327d97c80bd97d6378083c8d86505d094dec5103c2] [local: 172.22.10.202:5044, remote: 172.22.0.1:58304] Handling exception: io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate (caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate)
[2022-10-18T09:30:32,195][WARN][io.netty.channel.DefaultChannelPipeline][terza][8fb7acdb9937ab76f029df327d97c80bd97d6378083c8d86505d094dec5103c2] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate
````Preformatted text`
`````

---

<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: [November 15, 2022, 9:31am UTC](https://discuss.elastic.co/t/filebeat-and-logstash-ssl-config-is-correct/316868/3 "2022-11-15T09:31:29Z")

</div>

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