Hi there, I am currently doing a stack upgrade from 7.0.1 to 7.6.2. Everything went fine on the Elasticsearch cluster and Kibana instances but I have issues upgrading Logstash. To be precise, Logstash upgrade was fine, the issue I have is located in a pipeline and precisely in a Beats input (so lo…

I would appreciate if you can provide any insights about this @RobBavey ? Much appreciated!

Digging into this a bit further... Logstash 7.5.2 uses version 6.0.5 of the logstash-input-beats plugin Logstash 7.6.0 uses version 6.0.6 of the logstash-input-beats plugin Looking at the commits of version 6.0.5 (used by Logstash 7.5.2), we can see that the plugin used the following version of t…

@kuaaly Can you give a little more information? How did you generate the key? Is it protected with a password? Can you share your configuration, redacting any sensitive information that may be in there? Regards, Rob

Thanks for chiming in Rob! The key has been generated using this command and is not protected by any password openssl genrsa -out host1.key.pem 2048 The configuration is pretty simple: beats { port => 1234 ssl => true ssl_certificate => "/path/to/crt.pem" ssl_certificate_authorit…

@val Thanks for the update - The key needs to be in pkcs8 format, rather than pem - see the documentation for the beats input . Can you try that and see if you still see the error? Thanks, Rob

Hi Rob, thanks for your input. As far as the openssl documentation goes, what comes out of that command should be a PEM-encoded PKCS#8 RSA key. Moreover, I insist on the fact that the same key was previously working on 7.0.1, 7.4.2, and 7.5.2 versions. I also looked at the documentation page for th…

Hey, I tried reproducing but somehow all seems to be working (wout password protection). For simplicity, I've generated a cert + key pair using : openssl req -x509 -nodes -newkey rsa:4096 -keyout a_key.pem -out a_cert.pem -days 365 Than setup LS beats input and file-beats using the created ssl_ce…

When testing hypothesis, please keep in mind that, before the beats input 6.0.8 we didn't put the key itself to use unless a client connected to logstash. This means that just starting logstash isn't enough of a test when comparing Logstash 7.6.1 and previous versions. In this thread, @val I'm not …

@jsvd thanks for chiming in. What's important to note here is that it works on 7.0.1 but stops working on 7.6.0 without changing anything else than the stack version. We did not regenerate any key or certificate or anything. If we start any version of Logstash (7.0.1 up to 7.5.2), events are flowi…

What's important to note here is that it works on 7.0.1 but stops working on 7.6.0 without changing anything else than the stack version . We did not regenerate any key or certificate or anything. That is indeed something we're trying to solve and I agree it's a bug, but we've been struggling to…

Logstash-input-beats - File does not contain valid private key - #20 by system - Logstash

Topic		Replies	Views	Activity
Secure between Logstash and Filebeat - File does not contain valid private key Logstash windows	3	1623	June 27, 2022
Logstash beats input cant start with ssl enabled Logstash	4	789	October 26, 2020
Logstash (5.4.2) / Winlogbeat / SSL - File does not contain valid private key Logstash	2	3175	August 31, 2017
Can't get filebeat to talk to logstash 5.0 via TLS/SSL - PrivateKeyConverter.generatePkcs8 Logstash	8	1494	July 6, 2017
Looks like you either have a bad certificate, an invalid key or your private key was not in PKCS8 format in logstash Logstash	1	396	February 17, 2021