Jochen,
Thank you, again, for all the help looking into this problem for me.
Here is the output of the head -n1 command:
==> /etc/graylog/graylog-ssl/CERT.pem <==
-BEGIN CERTIFICATE-
==> /etc/graylog/graylog-ssl/KEY.pem <==
-BEGIN ENCRYPTED PRIVATE KEY-
I looked over the lo
Hi Dave,
the quotes around the password shouldn't be necessary (and are, in fact,
wrong). Could you please share the error message you've got when omitting
these quotes?
Please also post the output of the following command (it doesn't contain
any sensitive information, just the header of the p
Jochen,
I just got SSL all working recently as well.
You should not have to put the password in quotes. I didn't have to on my
setup.
Also, I'm fairly certain your cert or key aren't in the right formats. I
struggled for quite a while to get my cert into the right format but once I
did it
Jochen,
I ran the openssl command and it returned a single line with the text: RSA
key ok
I did have some errors prior to the current ones with Graylog not being
able to access the key file. Those turned out to the an incorrect
formatting in the server.conf file, I had to put the password in
Hi Dave,
the error message looks like the private key is in an incompatible or
invalid format which Graylog can't process.
Could you please share your Graylog configuration (the rest_* and web_*
settings should be sufficient) and the output of the following OpenSSL
command:
openssl rsa -noout
I have just started the process of deploying Graylog 2.0.3 and cannot say
anything about the process for settting up ssl within Graylog. if there
really is an issue with using the built in capabilities, you can always try
Apache as a proxy for Graylog.
https://www.lisenet.com/2015/install-grayl
