# Logstash (5.4.2) / Winlogbeat / SSL - File does not contain valid private key

**URL:** <https://discuss.elastic.co/t/logstash-5-4-2-winlogbeat-ssl-file-does-not-contain-valid-private-key/95183>\
**Category:** Logstash\
**Created:** [July 31, 2017, 12:21pm UTC](https://discuss.elastic.co/t/logstash-5-4-2-winlogbeat-ssl-file-does-not-contain-valid-private-key/95183 "2017-07-31T12:21:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jaypalexa](https://avatars.discourse-cdn.com/v4/letter/j/e56c9b/32.png) [@jaypalexa](https://discuss.elastic.co/u/jaypalexa)\
**Post date:** [August 3, 2017, 3:30pm UTC](https://discuss.elastic.co/t/logstash-5-4-2-winlogbeat-ssl-file-does-not-contain-valid-private-key/95183/2 "2017-08-03T15:30:17Z")

</div>

A co-worker discovered that OpenSSL 1.1.0f on our Debian 9 (Stretch) Logstash server box (Debian 4.9.30-2+deb9u1 (2017-06-18) x86\_64) was the source of our SSL certificate/key problem.

Another co-worker created the necessary certificates and keys on a different Debian 8 (Jessie) box with OpenSSL 1.0.1t and copied the certificates/keys to our Debian 9 (Stretch) Logstash server. We no longer see the errors reported in this issue.

Companion issue: [PKI between Logstash and Winlogbeat](https://discuss.elastic.co/t/pki-between-logstash-and-winlogbeat/94851)

---

_[View the full topic](https://discuss.elastic.co/t/logstash-5-4-2-winlogbeat-ssl-file-does-not-contain-valid-private-key/95183)._