# SSL Issues - NOT SSL/TLS RECORD

**URL:** <https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391>\
**Category:** Elasticsearch\
**Created:** [April 24, 2017, 9:39am UTC](https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391 "2017-04-24T09:39:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArthurMaroko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arthurmaroko/32/16789_2.png) [@ArthurMaroko](https://discuss.elastic.co/u/ArthurMaroko)\
**Post date:** [April 24, 2017, 9:39am UTC](https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391/1 "2017-04-24T09:39:39Z")

</div>

HI Guys

I'm a bit new to ElasticSearch. Did some reading and learning and so far so good.

I hit a dead point when I enabled my SSL settings in ElasticSearch. I'm using Windows 7. Kibana is able reach ElasticSearch, but I am unable to get any response from localhost:9200 via browser (not even a the .json file download when connection is established).

For some reason and according to the logs, my connection is being dropped. Below is the error message I'm getting server side).

[2017-04-24T12:09:51,462][WARN][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [node01] caught exception while handling client http traffic, closing connection [id: 0xd9ad62be, L:0.0.0.0/0.0.0.0:9200 ! R:/10.X00.XX.47:54251]  
io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record:

Client Side  
Error publishing events (retrying): get [http://10.X00.XX.49:9200](http://10.X00.XX.49:9200): EOF

Could someone one help me understand where I have gone wrong in my configurations? Did I generate my certs incorrectly? or Have I installed them incorrectly?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 24, 2017, 9:41am UTC](https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391/2 "2017-04-24T09:41:49Z")

</div>

SSL is not native to ES, so what are you using for that?

---

<div class="post-metadata">

**Author:** ![ArthurMaroko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arthurmaroko/32/16789_2.png) [@ArthurMaroko](https://discuss.elastic.co/u/ArthurMaroko)\
**Post date:** [April 24, 2017, 9:42am UTC](https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391/3 "2017-04-24T09:42:53Z")

</div>

X-Pack

Unless of course this doesn't answer the question?

---

<div class="post-metadata">

**Author:** ![ArthurMaroko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arthurmaroko/32/16789_2.png) [@ArthurMaroko](https://discuss.elastic.co/u/ArthurMaroko)\
**Post date:** [April 24, 2017, 10:30am UTC](https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391/4 "2017-04-24T10:30:39Z")

</div>

I figured out my problem. I had set my SSL configuration incorrectly. I applied the node cert Instead of applying the ca.crt and the protocol to https.

Thanks again  
Cheers

---

<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:** [May 22, 2017, 10:41am UTC](https://discuss.elastic.co/t/ssl-issues-not-ssl-tls-record/83391/5 "2017-05-22T10:41:00Z")

</div>

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