Crypto/rsa: verification error - using heartbeat

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.

What can be the issue here?

- type: http
  id: monitor-1
  name: monitor-1
  enabled: true
  schedule: '@every 60s'
  urls: [""]
  ipv4: true
  ipv6: true
  mode: any
  timeout: 15s
      'User-Agent': 'heartbeat'
  check.response.status: 200
  ssl.verification_mode: none

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.

This was changed in 7.6:
There won't be any changes / fixes for 7.4.

Is that closer to the behavior you are expecting?

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)

So what's the full error or stacktrace — just crypto/rsa error: verification error?

And I assume it's also not related to (I think we hit that internally on some demos).

Hi Philipp,
This is the full description I see in Uptime and in Discover:

Get crypto/rsa: verification error

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.