# Tips for failing handshake with shield **URL:** \ **Category:** Elasticsearch\ **Created:** [February 11, 2015, 4:54pm UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102 "2015-02-11T16:54:27Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Jettro\_Coenradie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jettro_coenradie/32/59704_2.png) [@Jettro\_Coenradie](https://discuss.elastic.co/u/Jettro_Coenradie)\ **Post date:** [February 11, 2015, 4:54pm UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102/1 "2015-02-11T16:54:27Z")
Hi, I am trying to get SSL/TLS to work on my raspberry pi cluster. To bad I get the following message: [2015-02-11 17:51:35,037][ERROR][shield.transport.netty] [jc-pi-red] SSL/TLS handshake failed, closing channel: null So I guess something is wrong in my certificate chain. I have created my own CA and followed the steps from the getting started guide. Any tips on how to start debugging? thanks Jettro -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cf83e1d4-10b8-47b2-a5a0-c5c2491dc899%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cf83e1d4-10b8-47b2-a5a0-c5c2491dc899%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jaymode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaymode/32/50103_2.png) [@jaymode](https://discuss.elastic.co/u/jaymode)\ **Post date:** [February 11, 2015, 6:05pm UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102/2 "2015-02-11T18:05:21Z")
There should be another message on the other end of the connection that has more details of the actual failure. That message can be seen on the client side of the connection when the connection was closed by the server side. Also, please see [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/shield/current/trouble-shooting.html#_sslhandshakeexception_causing_connections_to_fail) for common problems and some tips on how to resolve them. On Wednesday, February 11, 2015 at 8:54:27 AM UTC-8, Jettro Coenradie wrote: > Hi, > I am trying to get SSL/TLS to work on my raspberry pi cluster. To bad I > get the following message: > > [2015-02-11 17:51:35,037][ERROR][shield.transport.netty] [jc-pi-red] > SSL/TLS handshake failed, closing channel: null > > So I guess something is wrong in my certificate chain. I have created my > own CA and followed the steps from the getting started guide. Any tips on > how to start debugging? > > thanks > > Jettro -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jettro\_Coenradie\_2](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@Jettro\_Coenradie\_2](https://discuss.elastic.co/u/Jettro_Coenradie_2)\ **Post date:** [February 12, 2015, 7:20pm UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102/3 "2015-02-12T19:20:12Z")
Thanks Jay for your answer. Had a good look at the appendix with troubleshooting, but cannot really find something to help me out. On the client I see this message: [2015-02-12 20:10:28,363][ERROR][shield.transport.netty] [jc-pi-glas] SSL/TLS handshake failed, closing channel: null There is a stack trace after this error: [2015-02-12 20:10:28,264][WARN][shield.transport.netty] [jc-pi-glas] exception caught on transport layer [[id: 0x127799ce, /192.168.1.11:50409 =\> 192.168.1.10/192.168.1.10:9300]], closing connection java.lang.IllegalStateException: Internal error at sun.security.ssl.SSLEngineImpl.initHandshaker(SSLEngineImpl.java:464) at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1001) at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:901) at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:775) at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) at org.elasticsearch.common.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1285) at org.elasticsearch.common.netty.handler.ssl.SslHandler.decode(SslHandler.java:917) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.jav I also get numerous timeouts. The strange thing is that these timeout are pings to the node itself. [2015-02-12 20:10:25,151][WARN][discovery.zen.ping.unicast] [jc-pi-glas] failed to send ping to [[jc-pi-glas][RBV7\_u5yRsChF\_M8Ep2ICQ][jc-pi-glas][inet[ 192.168.1.11/192.168.1.11:9300]]] org.elasticsearch.transport.ReceiveTimeoutTransportException: [jc-pi-glas][inet[ 192.168.1.11/192.168.1.11:9300]][internal:discovery/zen/unicast] request\_id [5] timed out after [3751ms] at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:366) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) On the red pi I get this message: [2015-02-12 20:10:44,245][WARN][shield.transport.netty] [jc-pi-red] exception caught on transport layer [[id: 0xdc4d94e1, /192.168.1.11:50409 =\> /192.168.1.10:9300]], closing connection javax.net.ssl.SSLException: Received close\_notify during handshake at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1646) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1614) I also created a very small java application with sockets and used the same jks files to authenticate. There it works. Any other ideas? On Wed, Feb 11, 2015 at 7:05 PM, Jay Modi [jay.modi@elasticsearch.com](mailto:jay.modi@elasticsearch.com) wrote: > There should be another message on the other end of the connection that > has more details of the actual failure. That message can be seen on the > client side of the connection when the connection was closed by the server > side. > > Also, please see > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/shield/current/trouble-shooting.html#_sslhandshakeexception_causing_connections_to_fail) > for common problems and some tips on how to resolve them. > > On Wednesday, February 11, 2015 at 8:54:27 AM UTC-8, Jettro Coenradie > wrote: > > > Hi, > > I am trying to get SSL/TLS to work on my raspberry pi cluster. To bad I > > get the following message: > > > > [2015-02-11 17:51:35,037][ERROR][shield.transport.netty] [jc-pi-red] > > SSL/TLS handshake failed, closing channel: null > > > > So I guess something is wrong in my certificate chain. I have created my > > own CA and followed the steps from the getting started guide. Any tips on > > how to start debugging? > > > > thanks > > > > Jettro > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/g-AT4CAVBCw/unsubscribe](https://groups.google.com/d/topic/elasticsearch/g-AT4CAVBCw/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Jettro Coenradie > **[Gridshore](https://www.gridshore.nl/)** > > A weblog about software engineering, Architecture, Technology an other things we like. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CABB4caMUbzCHTUSn0VcQfiep24nMpYnweJ796\_s4N0bbc8F%2Biw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CABB4caMUbzCHTUSn0VcQfiep24nMpYnweJ796_s4N0bbc8F%2Biw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jaymode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaymode/32/50103_2.png) [@jaymode](https://discuss.elastic.co/u/jaymode)\ **Post date:** [February 13, 2015, 2:12am UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102/4 "2015-02-13T02:12:56Z")
I think you are running into the TLS handshake taking too long and it causes the pings to timeout and then the Netty channels are closed, which is why you see the connection closed messages. Since you are running on a Raspberry PI, the overhead of TLS is going to be a lot for that platform; the handshake is expensive in terms of CPU. You probably need to increase the zen ping timeout and based on your other post it may need to be like over 25 seconds. On Thursday, February 12, 2015 at 11:20:35 AM UTC-8, Jettro Coenradie wrote: > Thanks Jay for your answer. Had a good look at the appendix with > troubleshooting, but cannot really find something to help me out. On the > client I see this message: > > [2015-02-12 20:10:28,363][ERROR][shield.transport.netty] [jc-pi-glas] > SSL/TLS handshake failed, closing channel: null > > There is a stack trace after this error: > [2015-02-12 20:10:28,264][WARN][shield.transport.netty] [jc-pi-glas] > exception caught on transport layer [[id: 0x127799ce, /192.168.1.11:50409 > =\> 192.168.1.10/192.168.1.10:9300] > [http://192.168.1.10/192.168.1.10:9300]](http://192.168.1.10/192.168.1.10:9300%5D)], closing connection > java.lang.IllegalStateException: Internal error > at sun.security.ssl.SSLEngineImpl.initHandshaker(SSLEngineImpl.java:464) > at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1001) > at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:901) > at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:775) > at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) > at > org.elasticsearch.common.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1285) > at > org.elasticsearch.common.netty.handler.ssl.SslHandler.decode(SslHandler.java:917) > at > org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.jav > > I also get numerous timeouts. The strange thing is that these timeout are > pings to the node itself. > > [2015-02-12 20:10:25,151][WARN][discovery.zen.ping.unicast] [jc-pi-glas] > failed to send ping to > [[jc-pi-glas][RBV7\_u5yRsChF\_M8Ep2ICQ][jc-pi-glas][inet[ > 192.168.1.11/192.168.1.11:9300] [http://192.168.1.11/192.168.1.11:9300]](http://192.168.1.11/192.168.1.11:9300%5D) > ]] > org.elasticsearch.transport.ReceiveTimeoutTransportException: > [jc-pi-glas][inet[ > 192.168.1.11/192.168.1.11:9300]][internal:discovery/zen/unicast > [http://192.168.1.11/192.168.1.11:9300]][internal:discovery/zen/unicast](http://192.168.1.11/192.168.1.11:9300%5D%5D%5Binternal:discovery/zen/unicast)] > request\_id [5] timed out after [3751ms] > at > org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:366) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > > On the red pi I get this message: > [2015-02-12 20:10:44,245][WARN][shield.transport.netty] [jc-pi-red] > exception caught on transport layer [[id: 0xdc4d94e1, /192.168.1.11:50409 > =\> /192.168.1.10:9300]], closing connection > javax.net.ssl.SSLException: Received close\_notify during handshake > at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) > at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1646) > at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1614) > > I also created a very small java application with sockets and used the > same jks files to authenticate. There it works. > > Any other ideas? > > On Wed, Feb 11, 2015 at 7:05 PM, Jay Modi \<[jay....@elasticsearch.com](mailto:jay....@elasticsearch.com) > \\> wrote: > > > There should be another message on the other end of the connection that > > has more details of the actual failure. That message can be seen on the > > client side of the connection when the connection was closed by the server > > side. > > > > Also, please see > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/shield/current/trouble-shooting.html#_sslhandshakeexception_causing_connections_to_fail) > > for common problems and some tips on how to resolve them. > > > > On Wednesday, February 11, 2015 at 8:54:27 AM UTC-8, Jettro Coenradie > > wrote: > > > > > Hi, > > > I am trying to get SSL/TLS to work on my raspberry pi cluster. To bad I > > > get the following message: > > > > > > [2015-02-11 17:51:35,037][ERROR][shield.transport.netty] [jc-pi-red] > > > SSL/TLS handshake failed, closing channel: null > > > > > > So I guess something is wrong in my certificate chain. I have created my > > > own CA and followed the steps from the getting started guide. Any tips on > > > how to start debugging? > > > > > > thanks > > > > > > Jettro > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/g-AT4CAVBCw/unsubscribe](https://groups.google.com/d/topic/elasticsearch/g-AT4CAVBCw/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > Jettro Coenradie > [http://www.gridshore.nl](http://www.gridshore.nl) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7308bc30-f3bc-4634-b292-bac9615a259f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7308bc30-f3bc-4634-b292-bac9615a259f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jettro\_Coenradie\_2](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@Jettro\_Coenradie\_2](https://discuss.elastic.co/u/Jettro_Coenradie_2)\ **Post date:** [February 13, 2015, 7:55am UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102/5 "2015-02-13T07:55:43Z")
Hi Jay, thanks again for the help. You were so right. Change the timeout to 30s and now the cluster is up and running. Now I can go for the next steps. regards Jettro On Fri, Feb 13, 2015 at 3:12 AM, Jay Modi [jay.modi@elasticsearch.com](mailto:jay.modi@elasticsearch.com) wrote: > I think you are running into the TLS handshake taking too long and it > causes the pings to timeout and then the Netty channels are closed, which > is why you see the connection closed messages. Since you are running on a > Raspberry PI, the overhead of TLS is going to be a lot for that platform; > the handshake is expensive in terms of CPU. You probably need to increase > the zen ping timeout and based on your other post it may need to be like > over 25 seconds. > > On Thursday, February 12, 2015 at 11:20:35 AM UTC-8, Jettro Coenradie > wrote: > > > Thanks Jay for your answer. Had a good look at the appendix with > > troubleshooting, but cannot really find something to help me out. On the > > client I see this message: > > > > [2015-02-12 20:10:28,363][ERROR][shield.transport.netty] [jc-pi-glas] > > SSL/TLS handshake failed, closing channel: null > > > > There is a stack trace after this error: > > [2015-02-12 20:10:28,264][WARN][shield.transport.netty] [jc-pi-glas] > > exception caught on transport layer [[id: 0x127799ce, /192.168.1.11:50409 > > =\> 192.168.1.10/192.168.1.10:9300] > > [http://192.168.1.10/192.168.1.10:9300]](http://192.168.1.10/192.168.1.10:9300%5D)], closing connection > > java.lang.IllegalStateException: Internal error > > at sun.security.ssl.SSLEngineImpl.initHandshaker(SSLEngineImpl.java:464) > > at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1001) > > at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:901) > > at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:775) > > at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) > > at org.elasticsearch.common.netty.handler.ssl.SslHandler. > > unwrap(SslHandler.java:1285) > > at org.elasticsearch.common.netty.handler.ssl.SslHandler. > > decode(SslHandler.java:917) > > at org.elasticsearch.common.netty.handler.codec.frame. > > FrameDecoder.callDecode(FrameDecoder.jav > > > > I also get numerous timeouts. The strange thing is that these timeout are > > pings to the node itself. > > > > [2015-02-12 20:10:25,151][WARN][discovery.zen.ping.unicast] [jc-pi-glas] > > failed to send ping to [[jc-pi-glas][RBV7\_u5yRsChF\_ > > M8Ep2ICQ][jc-pi-glas][inet[192.168.1.11/192.168.1.11:9300] > > [http://192.168.1.11/192.168.1.11:9300]](http://192.168.1.11/192.168.1.11:9300%5D)]] > > org.elasticsearch.transport.ReceiveTimeoutTransportException: > > [jc-pi-glas][inet[192.168.1.11/192.168.1.11:9300]][ > > internal:discovery/zen/unicast > > [http://192.168.1.11/192.168.1.11:9300]][internal:discovery/zen/unicast](http://192.168.1.11/192.168.1.11:9300%5D%5D%5Binternal:discovery/zen/unicast)] > > request\_id [5] timed out after [3751ms] > > at org.elasticsearch.transport.TransportService$TimeoutHandler.run( > > TransportService.java:366) > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > ThreadPoolExecutor.java:1142) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:744) > > > > On the red pi I get this message: > > [2015-02-12 20:10:44,245][WARN][shield.transport.netty] [jc-pi-red] > > exception caught on transport layer [[id: 0xdc4d94e1, /192.168.1.11:50409 > > =\> /192.168.1.10:9300]], closing connection > > javax.net.ssl.SSLException: Received close\_notify during handshake > > at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) > > at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1646) > > at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1614) > > > > I also created a very small java application with sockets and used the > > same jks files to authenticate. There it works. > > > > Any other ideas? > > > > On Wed, Feb 11, 2015 at 7:05 PM, Jay Modi [jay....@elasticsearch.com](mailto:jay....@elasticsearch.com) > > wrote: > > > > > There should be another message on the other end of the connection that > > > has more details of the actual failure. That message can be seen on the > > > client side of the connection when the connection was closed by the server > > > side. > > > > > > Also, please see [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/shield/current/) > > > trouble-shooting.html#\_sslhandshakeexception\_causing\_connections\_to\_fail > > > for common problems and some tips on how to resolve them. > > > > > > On Wednesday, February 11, 2015 at 8:54:27 AM UTC-8, Jettro Coenradie > > > wrote: > > > > > > > Hi, > > > > I am trying to get SSL/TLS to work on my raspberry pi cluster. To bad I > > > > get the following message: > > > > > > > > [2015-02-11 17:51:35,037][ERROR][shield.transport.netty] > > > > [jc-pi-red] SSL/TLS handshake failed, closing channel: null > > > > > > > > So I guess something is wrong in my certificate chain. I have created > > > > my own CA and followed the steps from the getting started guide. Any tips > > > > on how to start debugging? > > > > > > > > thanks > > > > > > > > Jettro > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > topic/elasticsearch/g-AT4CAVBCw/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/652d10f6-79ee-45a5-b919-eca3bc15a5d6%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > Jettro Coenradie > > [http://www.gridshore.nl](http://www.gridshore.nl) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/g-AT4CAVBCw/unsubscribe](https://groups.google.com/d/topic/elasticsearch/g-AT4CAVBCw/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/7308bc30-f3bc-4634-b292-bac9615a259f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7308bc30-f3bc-4634-b292-bac9615a259f%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/7308bc30-f3bc-4634-b292-bac9615a259f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7308bc30-f3bc-4634-b292-bac9615a259f%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Jettro Coenradie > **[Gridshore](https://www.gridshore.nl/)** > > A weblog about software engineering, Architecture, Technology an other things we like. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CABB4caN3PUaUBi6sVh9j9hDM7xyqxGwjPw3Sb7iW4DLUJsjRRw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CABB4caN3PUaUBi6sVh9j9hDM7xyqxGwjPw3Sb7iW4DLUJsjRRw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:33am UTC](https://discuss.elastic.co/t/tips-for-failing-handshake-with-shield/22102/6 "2017-07-06T00:33:02Z")