# Hitting error getting heartbeat from Elasticsearch with SSL

**URL:** <https://discuss.elastic.co/t/hitting-error-getting-heartbeat-from-elasticsearch-with-ssl/184245>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [June 4, 2019, 7:24pm UTC](https://discuss.elastic.co/t/hitting-error-getting-heartbeat-from-elasticsearch-with-ssl/184245 "2019-06-04T19:24:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\
**Post date:** [June 4, 2019, 7:24pm UTC](https://discuss.elastic.co/t/hitting-error-getting-heartbeat-from-elasticsearch-with-ssl/184245/1 "2019-06-04T19:24:18Z")

</div>

This as working fine vefore converting to https. I have tried a number of modifications but still stuck on getting this to work. Below is my error and heartbeat configuration

[2019-06-04T19:21:17,067][WARN][o.e.h.AbstractHttpServerTransport] [rrc101-196516-elasticsearch-70test1] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=0.0.0.0/0.0.0.0:9200, remoteAddress=/35.185.109.39:50424}  
io.netty.handler.codec.DecoderException: io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 474554202f20485454502f312e310d0a486f73743a2033352e3139362e31382e32343a393230300d0a557365722d4167656e743a20476f2d687474702d636c69656e742f312e310d0a436f6e6e656374696f6e3a20636c6f73650d0a0d0a

- type: http  
schedule: "@every 30s"  
urls: ["[https://34.73.241.5:9200](https://34.73.241.5:9200)"]  
username: beats\_system  
password: \*\*\*\*\*\*\*\*  
ssl:  
certificate\_authorities: ['/home/ffoti/rrc101-196516-70tst.crt']  
verification\_mode: none  
supported\_protocols: ["TLSv1.0", "TLSv1.1", "TLSv1.2"]  
check.response.status: 200  
fields:  
environment: "rrc101-196516"  
hostname: rrc101-196516-elasticsearch-70test1  
service: elasticsearch

---

<div class="post-metadata">

**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\
**Post date:** [June 6, 2019, 5:26pm UTC](https://discuss.elastic.co/t/hitting-error-getting-heartbeat-from-elasticsearch-with-ssl/184245/2 "2019-06-06T17:26:38Z")

</div>

We resolved the ssl error but now there are no errors and heartbeat is still reporting Elasticsearch DOWN. Any Ideas?

- type: http  
schedule: "@every 30s"  
urls: ["[https://35.196.18.24:9200](https://35.196.18.24:9200)"]  
#check.response.status: 200  
check.request:  
method: GET  
check.response:
# status: 200
json:  
- description: check status  
condition:  
equals:  
status: ok  
elasticsearch.username: remote\_monitoring\_user  
elasticsearch.password: \*\*\*\*\*\*\*\*\*  
ssl:  
certificate\_authorities: "/etc/heartbeat/heartbeat.pem"  
verification\_mode: full  
fields:  
environment: "rrc101-196516"  
hostname: rrc101-196516-elasticsearch-70test1  
service: elasticsearch

---

<div class="post-metadata">

**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\
**Post date:** [June 6, 2019, 5:55pm UTC](https://discuss.elastic.co/t/hitting-error-getting-heartbeat-from-elasticsearch-with-ssl/184245/3 "2019-06-06T17:55:05Z")

</div>

Resolved. There was a typo on username and password. Removed "elasticsearch." and heartbeat is working

---

<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:** [July 4, 2019, 5:56pm UTC](https://discuss.elastic.co/t/hitting-error-getting-heartbeat-from-elasticsearch-with-ssl/184245/4 "2019-07-04T17:56:59Z")

</div>

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