# Logstash 7.5 with SSL giving SSLV3\_ALERT\_BAD\_CERTIFICATE

**URL:** <https://discuss.elastic.co/t/logstash-7-5-with-ssl-giving-sslv3-alert-bad-certificate/212512>\
**Category:** Logstash\
**Tags:** elastic-stack-security\
**Created:** [December 19, 2019, 3:41pm UTC](https://discuss.elastic.co/t/logstash-7-5-with-ssl-giving-sslv3-alert-bad-certificate/212512 "2019-12-19T15:41:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [December 20, 2019, 6:13am UTC](https://discuss.elastic.co/t/logstash-7-5-with-ssl-giving-sslv3-alert-bad-certificate/212512/3 "2019-12-20T06:13:35Z")

</div>

> [@alesanchez](#):
>
> io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: error:10000412:SSL routines:OPENSSL\_internal:SSLV3\_ALERT\_BAD\_CERTIFICATE

This is an SSL _alert_.  
Alerts are sent from one party in the connection to the other party to inform them that they detected a problem. Typically these are fatal, and the first party then terminates the connection.

In this case Logstash is reporting that it received an alert from someone (probably beats, since that's the only input you have) that says "I don't trust your certificate".

Which means the issue here is that beats is not configured to trust the certificate that Logstash provides.  
You probably need to modify the beats config to include `ss.certificate_authorities`

---

_[View the full topic](https://discuss.elastic.co/t/logstash-7-5-with-ssl-giving-sslv3-alert-bad-certificate/212512)._