SSL Handshake Issue

(Ashwin Gupta) #1

I am facing a lot of issues to make my Forwarder work even after all steps supposedly followed. Have also been browsing and following tips from - but have not turned lucky yet.

The worst part is that, it has already taken much more time for me to make Forwarder work than it took me for complete setup of Logstash+Kiban+Elasticsearch all together...little sarcatic that is but true!

I've also been exploring the alternatives to logstash-forwarder but still found none that gets on-board fast and easy.

I am very keen to make my forwarder work out but not able to due to the ssl handshake issue.

Can any one help me with the possible reasons for my forwarder (on RHEL 6) not able to work with my Logstash server cert file and throwing the below error everytime?

2015/06/07 15:47:23.964418 Setting trusted CA from file: /usr/bin/mw_lumberjack.crt
2015/06/07 15:47:23.966107 Connecting to []:10010 (
2015/06/07 15:47:23.971762 Failed to tls handshake with x509: certificate is valid for , not

Pasting the config and cert details below.

Cert Excerpt:-
Signature Algorithm: sha1WithRSAEncryption

        Not Before: Jun  5 12:24:20 2015 GMT
        Not After : Jun  4 12:24:20 2016 GMT

Forwarder Config File:-
"network": {
# A list of downstream servers listening for our messages.
# logstash-forwarder will pick one at random and only switch if
# the selected one appears to be dead or unresponsive
"servers": [ "" ],

##"ssl certificate": "./logstash-forwarder.crt",
##"ssl key": "./logstash-forwarder.key",

"ssl ca": "/usr/bin/mw_lumberjack.crt",

I've already tried other options of mentioning the issuer's FQDN differently in the cert but NO luck.

Any help will be very appreciated and help me run the successful PoC.

(Mark Walkom) #2

This looks like a certificate problem.

What are the commands you used to create the cert?

(Ashwin Gupta) #3

Continuing the discussion from SSL Handshake Issue:

I doubt but still hoping that is the issue. Please find below the command used for creating the cert.

openssl req -x509 -batch -nodes -newkey rsa:2048 -keyout mw_lumberjack.key -out mw_lumberjack.crt -subj '/CN=*'

Just to recap the setup - I've the key and the cert on my Logstash Server side. Logstash server, with forwarder input, is started on the given port on the server.
###tcp 0 0* LISTEN

The cert file is transfered to the forwarder side, and the forwarder is attempted to start up with the cert file passed as the ca cert file in configurations.

Please let me know if you observe any mistake there.

(Mark Walkom) #4

I don't think you can use wildcards, try using a specific name.

(Ashwin Gupta) #5

That is what I've tried as first thing before trying out *.* and **.Domain and *.Domain etc.

(system) #6