# TLS handshake timeout using 6.5.1 docker images

**URL:** <https://discuss.elastic.co/t/tls-handshake-timeout-using-6-5-1-docker-images/159633>\
**Category:** Elasticsearch\
**Created:** [December 6, 2018, 2:11am UTC](https://discuss.elastic.co/t/tls-handshake-timeout-using-6-5-1-docker-images/159633 "2018-12-06T02:11:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ronchav](https://avatars.discourse-cdn.com/v4/letter/r/35a633/32.png) [@ronchav](https://discuss.elastic.co/u/ronchav)\
**Post date:** [December 6, 2018, 2:11am UTC](https://discuss.elastic.co/t/tls-handshake-timeout-using-6-5-1-docker-images/159633/1 "2018-12-06T02:11:52Z")

</div>

Hi,

I have docker for windows and I am running 3 elastic containers and 1 kibana on version 6.5.1 and they are communicating well over TLS/SSL setup. I was able to browse dashboard and other features in Kibana but at some point I am getting TLS handshake timeout and the connection cannot recover anymore.

One use case I have is when I click the Infrastructure on the left menu (as per log below) and go further, communication will be disconnected. Any idea about this problem?

{"type":"response","@timestamp":"2018-12-05T09:13:18Z","tags":,"pid":1,"method":"get","statusCode":304,"req":{"url":"/plugins/apm/icon.svg","method":"get","headers":{"host":"kibana.local:5601","connection":"keep-alive","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36","accept":"image/webp,image/apng,image/_,_/\*;q=0.8","referer":"[https://kibana.local:5601/app/infra","accept-encoding":"gzip](https://kibana.local:5601/app/infra%22,%22accept-encoding%22:%22gzip), deflate, br","accept-language":"en-US,en;q=0.9,es;q=0.8","if-none-match":""cdb6515bc1340e806d4f17cbeea6a51eb5f40732-gzip"","if-modified-since":"Fri, 16 Nov 2018 02:38:53 GMT"},"remoteAddress":"192.168.1.1","userAgent":"192.168.1.1","referer":"[https://kibana.local:5601/app/infra"},"res":{"statusCode":304,"responseTime":2,"contentLength":9},"message":"GET](https://kibana.local:5601/app/infra%22%7D,%22res%22:%7B%22statusCode%22:304,%22responseTime%22:2,%22contentLength%22:9%7D,%22message%22:%22GET) /plugins/apm/icon.svg 304 2ms - 9.0B"}  
{"type":"error","@timestamp":"2018-12-05T09:15:18Z","tags":["connection","client","error"],"pid":1,"level":"error","error":{"message":"TLS handshake timeout","name":"Error","stack":"Error: TLS handshake timeout\n at TLSSocket.\_handleTimeout (\_tls\_wrap.js:592:22)\n at Object.onceWrapper (events.js:313:30)\n at emitNone (events.js:106:13)\n at TLSSocket.emit (events.js:208:7)\n at TLSSocket.Socket.\_onTimeout (net.js:410:8)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)"},"message": **"TLS handshake timeout"}**  
{"type":"error","@timestamp":"2018-12-05T09:15:18Z","tags":["connection","client","error"],"pid":1,"level":"error","error":{"message":"TLS handshake timeout","name":"Error","stack":"Error: TLS handshake timeout\n at TLSSocket.\_handleTimeout (\_tls\_wrap.js:592:22)\n at Object.onceWrapper (events.js:313:30)\n at emitNone (events.js:106:13)\n at TLSSocket.emit (events.js:208:7)\n at TLSSocket.Socket.\_onTimeout (net.js:410:8)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)"},"message": **"TLS handshake timeout"}**

 ![1](https://us1.discourse-cdn.com/elastic/original/3X/b/f/bf642bee38bd1de6d30d4a2d6fabebd287685a1c.jpeg) ![1_unreachable](https://us1.discourse-cdn.com/elastic/original/3X/3/8/382380536145646d7b8d7e5c11aa36f81f96f62f.jpeg)

---

<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:** [January 3, 2019, 2:11am UTC](https://discuss.elastic.co/t/tls-handshake-timeout-using-6-5-1-docker-images/159633/2 "2019-01-03T02:11:53Z")

</div>

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