# Crypto/rsa: verification error - using heartbeat
**URL:** https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427
**Category:** Beats
**Created:** [July 1, 2020, 7:43am UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427 "2020-07-01T07:43:47Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Peter\_Steenbergen](https://discuss.elastic.co/u/Peter_Steenbergen)
#### Post date: [July 1, 2020, 7:43am UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/1 "2020-07-01T07:43:48Z")
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.
What can be the issue here?
```
- type: http
id: monitor-1
name: monitor-1
enabled: true
schedule: '@every 60s'
urls: ["https://marccornelius.nl/"]
ipv4: true
ipv6: true
mode: any
timeout: 15s
check.request:
headers:
'User-Agent': 'heartbeat'
check.response.status: 200
ssl.verification_mode: none
```
---
### Author:  [@xeraa](https://discuss.elastic.co/u/xeraa)
#### Post date: [July 2, 2020, 11:46am UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/2 "2020-07-02T11:46:03Z")
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?
---
### Author:  [@Peter\_Steenbergen](https://discuss.elastic.co/u/Peter_Steenbergen)
#### Post date: [July 2, 2020, 12:09pm UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/3 "2020-07-02T12:09:40Z")
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.
---
### Author:  [@xeraa](https://discuss.elastic.co/u/xeraa)
#### Post date: [July 2, 2020, 12:25pm UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/4 "2020-07-02T12:25:41Z")
This was changed in 7.6: [https://github.com/elastic/beats/pull/14125](https://github.com/elastic/beats/pull/14125)
There won't be any changes / fixes for 7.4.
Is that closer to the behavior you are expecting?
---
### Author:  [@Peter\_Steenbergen](https://discuss.elastic.co/u/Peter_Steenbergen)
#### Post date: [July 2, 2020, 12:47pm UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/5 "2020-07-02T12:47:11Z")
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)
---
### Author:  [@xeraa](https://discuss.elastic.co/u/xeraa)
#### Post date: [July 3, 2020, 12:51am UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/6 "2020-07-03T00:51:01Z")
So what's the full error or stacktrace — just `crypto/rsa error: verification error`?
And I assume it's also not related to [https://github.com/elastic/beats/issues/17123](https://github.com/elastic/beats/issues/17123) (I think we hit that internally on some demos).
---
### Author:  [@Peter\_Steenbergen](https://discuss.elastic.co/u/Peter_Steenbergen)
#### Post date: [July 3, 2020, 7:21am UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/7 "2020-07-03T07:21:31Z")
Hi Philipp,
This is the full description I see in Uptime and in Discover:
Error
Get [https://www.marccornelius.nl/:](https://www.marccornelius.nl/:) 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.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 31, 2020, 9:21am UTC](https://discuss.elastic.co/t/crypto-rsa-verification-error-using-heartbeat/239427/8 "2020-07-31T09:21:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.