# TLS errors

**URL:** <https://discuss.elastic.co/t/tls-errors/260996>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [January 13, 2021, 12:28pm UTC](https://discuss.elastic.co/t/tls-errors/260996 "2021-01-13T12:28:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaulRudin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paulrudin/32/82177_2.png) [@PaulRudin](https://discuss.elastic.co/u/PaulRudin)\
**Post date:** [January 13, 2021, 12:28pm UTC](https://discuss.elastic.co/t/tls-errors/260996/1 "2021-01-13T12:28:16Z")

</div>

Hi, I've used eck to get ES and Kibana up. This seem to be running OK, but I disabled tls for the communication between kibana and ES: by putting spec.http.tls.selfSignedCertificate.disabled to true and I'm seeing errors like this in the kibana logs:  
`{"type":"log","@timestamp":"2021-01-13T12:11:03Z","tags": ["error","elasticsearch","data"],"pid":6,"message":"[ConnectionError]: write EPROTO 140529811875648:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:\n"}`

So, given that I can use kibana and make queries and so forth - what problem are the logs telling me about and how can I fix it?

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [January 14, 2021, 3:43pm UTC](https://discuss.elastic.co/t/tls-errors/260996/2 "2021-01-14T15:43:55Z")

</div>

Hi, could you share the version of ECK you are using and the Elasticsearch and the Kibana manifests ?

Thanks

---

<div class="post-metadata">

**Author:** ![PaulRudin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paulrudin/32/82177_2.png) [@PaulRudin](https://discuss.elastic.co/u/PaulRudin)\
**Post date:** [January 14, 2021, 5:35pm UTC](https://discuss.elastic.co/t/tls-errors/260996/3 "2021-01-14T17:35:12Z")

</div>

Yesterday I tore it all down and reapplied my up to date manifests and the issue has gone away. I guess the problem was an artifact of having changed things a few times since setting it up (initially I just had the defaults, and then I turned off the tls for the in-cluster http).

---

<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:** [November 4, 2022, 8:21am UTC](https://discuss.elastic.co/t/tls-errors/260996/4 "2022-11-04T08:21:32Z")

</div>