# OpenSSL failed to parse encrypted private key

**URL:** <https://discuss.elastic.co/t/openssl-failed-to-parse-encrypted-private-key/309584>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 13, 2022, 10:35pm UTC](https://discuss.elastic.co/t/openssl-failed-to-parse-encrypted-private-key/309584 "2022-07-13T22:35:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jocha](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jocha](https://discuss.elastic.co/u/jocha)\
**Post date:** [July 13, 2022, 10:35pm UTC](https://discuss.elastic.co/t/openssl-failed-to-parse-encrypted-private-key/309584/1 "2022-07-13T22:35:13Z")

</div>

Hello,  
Is this issue from before still a problem with filebeats? [Filebeat private key parse error - #6 by adrisr](https://discuss.elastic.co/t/filebeat-private-key-parse-error/119633/6)

Also running on openssl version 1.x, when using encrypted pem key with key\_passphrase getting:

```auto
Exiting: error initializing publisher: 1 error: tls: failed to parse private key

```

```auto
  
  ssl.certificate_authorities: ["/etc/pki/cert"]
  ssl.certificate: /etc/pki/logstash.cer
  ssl.key: /etc/pki/logstash.key
  ssl.key_passphrase: "Password"

```

I see no problem when Logstash or Elasticearch uses encrypted pem keys

---

<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:** [August 11, 2022, 12:35am UTC](https://discuss.elastic.co/t/openssl-failed-to-parse-encrypted-private-key/309584/2 "2022-08-11T00:35:29Z")

</div>

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