# Logstash Lumberjack Cert

**URL:** <https://discuss.elastic.co/t/logstash-lumberjack-cert/174885>\
**Category:** Logstash\
**Created:** [April 1, 2019, 10:29pm UTC](https://discuss.elastic.co/t/logstash-lumberjack-cert/174885 "2019-04-01T22:29:21Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gruselglatz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gruselglatz/32/42675_2.png) [@gruselglatz](https://discuss.elastic.co/u/gruselglatz)\
**Post date:** [April 3, 2019, 1:20pm UTC](https://discuss.elastic.co/t/logstash-lumberjack-cert/174885/4 "2019-04-03T13:20:42Z")

</div>

I am in the same situation as you. I configured everything like here: [https://www.elastic.co/guide/en/logstash/current/ls-to-ls.html](https://www.elastic.co/guide/en/logstash/current/ls-to-ls.html)

But i get sometimes PEER\_DID\_NOT\_RETURN\_A\_CERTIFICATE or SSLV3\_ALERT\_CERTIFICATE\_UNKNOWN

my configs:  
upstream:

```
output {
  lumberjack {
    hosts => "agg_hag1.domain.com"
    port => 5055
    ssl_certificate => "/home/logstash/certs/agg_hag1.crt"
    codec => "json"
  }
}

```

downstream:

```
input {
  beats {
    port => 5055
    codec => "json"
    ssl => true
    ssl_certificate => "/home/logstash/certs/agg_hag1.crt"
    ssl_certificate_authorities => "/home/logstash/certs/domain-ca-pem.crt"
    ssl_key => "/home/logstash/certs/agg_hag1-des-v1.pem"
    ssl_key_passphrase => "PWD"
# ssl_verify_mode => none
# tls_min_version => 1.2
  }
}
```

---

_[View the full topic](https://discuss.elastic.co/t/logstash-lumberjack-cert/174885)._
