# HearBeat monitor throwing IP SANS error

**URL:** <https://discuss.elastic.co/t/hearbeat-monitor-throwing-ip-sans-error/272916>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [May 13, 2021, 2:15pm UTC](https://discuss.elastic.co/t/hearbeat-monitor-throwing-ip-sans-error/272916 "2021-05-13T14:15:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohitarorait82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitarorait82/32/82981_2.png) [@rohitarorait82](https://discuss.elastic.co/u/rohitarorait82)\
**Post date:** [May 13, 2021, 2:15pm UTC](https://discuss.elastic.co/t/hearbeat-monitor-throwing-ip-sans-error/272916/1 "2021-05-13T14:15:00Z")

</div>

Hi All,

I am trying to implement hearbeat monitor for one of my application and I am getting below error.

I have done below configuration

```
- type: http

  # List or urls to query
  urls: ["https://x.x.x.x:9090"]
  # Configure task schedule
  schedule: '@every 10s'
  InsecureSkipVerify: true
  # Total test connection and data exchange timeout
  #timeout: 16s
  ssl:
  # Certificate Authorities
   certificate_authorities:
     - |
       -----BEGIN CERTIFICATE-----
       some base64 encoded value
-----END CERTIFICATE-----

```

**Error**  
Get "[https://x.x.x.x:9090](https://x.x.x.x:9090)": x509: cannot validate certificate for x.x.x.x because it doesn't contain any IP SANs

One of the reason can be cn name is different than the host name, but I am not whether this is the reason and also how to resolve it

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [May 13, 2021, 8:17pm UTC](https://discuss.elastic.co/t/hearbeat-monitor-throwing-ip-sans-error/272916/2 "2021-05-13T20:17:41Z")

</div>

It looks like you're pinging an IP instead of a domain. You'll need the URL to be the actual hostname of the service you're testing rather than an IP. TLS certificates only match domains not IPs unless you have specified in IP subject alternative name which you have not.

Is there a reason you're pinging the IP and not the hostname?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 10, 2021, 10:18pm UTC](https://discuss.elastic.co/t/hearbeat-monitor-throwing-ip-sans-error/272916/3 "2021-06-10T22:18:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.