Hi,
I am getting a crypto/rsa error: verification error with heartbeat version 7.4.2.
The website is using LetsEncrypt and the SSL was verified with ssllabs with a grade of A.
So the problem is that you have set ssl.verification_mode: none and you still get a verification error? Or that you get a verification error for a certificate that should actually be valid?
The heartbeat gives an error, but not a logical one. All the browsers are redirecting to the www. variant of that domain correctly.
So I would expect that the error would be: Received status of 301 should be 200 error.
In this case it seems that the certificate is not matching the domain (server signed looks like it) and gives some kind of crypto-error. With the SSL verification_mode to false I would guess that there should not a crypto error based on the SSL.
Hmm this is for the redirects. The redirects is a step further. In this case the host gives prematurely an error based on the crypto of the domain. The HTTP.go client gives the error (or seems like it)
I will try a newer version later this weekend. But there was a reason I am using 7.4.2 because with newer version when a yml is not correct all the other ymls will also skipped and heartbeat will not run.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.