sslv3 alert bad certificate after hardware changes
Just replace some hardware on my puppet master, new motherboard.
Everything seems to be working just fine, however all my puppets are consistently failing with "sslv3 alert bad certificate".
I have read a lot of threads the simply encourage to delete all certificates and generate new ones. But I have a serious problem with that, I like to understand why things happen. Also, I hate to run things by hand on my nodes, that is why a got Puppet in the first place, this keeps happening from time to time, etc...
So, I am digging deeper to check what is going on.
If I run puppet agent -t, I get the error: SSL_connect returned=1 state=SSLv3 read server session ticket A: sslv3 alert bad certificate.
However, both client and server have the same ca certificate, nothing seems to have changed, by just digging a bit into the files.
I also run by hand the following command from the node:
openssl s_client -connect puppet:8140 -CAFile my-puppet-ca.pem
And I get a nice Verify return code: 0 (OK).
So, the problem does not seem to be the actual certificates, but something "puppety" going on...
any idea what could be going on?
I run puppet 3.8.x on Ubuntu.