# Elasticsearch https secure communication

**URL:** <https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [January 29, 2020, 10:20am UTC](https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978 "2020-01-29T10:20:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\
**Post date:** [January 29, 2020, 10:20am UTC](https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978/1 "2020-01-29T10:20:11Z")

</div>

Hi All,

I have secured my cluster's (3 nodes) http communication as below:  
xpack.security.enabled: true  
xpack.security.transport.ssl.enabled: true  
xpack.security.transport.ssl.verification\_mode: certificate  
xpack.security.transport.ssl.keystore.path: /etc/elasticsearch/cert/elastic-certificates.p12  
xpack.security.transport.ssl.truststore.path: /etc/elasticsearch/cert/elastic-certificates.p12  
xpack.security.http.ssl.enabled: true  
xpack.security.http.ssl.keystore.path: /etc/elasticsearch/cert/elastic-certificates.p12  
xpack.security.http.ssl.truststore.path: /etc/elasticsearch/cert/elastic-certificates.p12  
(The certificates are generated with elasticsearch-certutil. I have copied the same certs to all nodes.)  
Everything work fine, but my logs are full of WARNs like below (cluster's IP addresses between xxx.xxx.xxx.210 and xxx.xxx.xxx.212):

> [2020-01-29T11:04:04,170][WARN][o.e.h.AbstractHttpServerTransport] [abc-i-elastic03] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/xxx.xxx.xxx.212:9200, remoteAddress=/xxx.xxx.xxx.211:55756}  
> io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad\_certificate

Version: 7.5.2

Please help me how to avoid these warnings. Thanks!

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [January 29, 2020, 10:57am UTC](https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978/2 "2020-01-29T10:57:47Z")

</div>

Something in `xxx.xxx.xxx.211:55756` is attempting to connect to Elasticsearch over HTTP over TLS on port 9200 and fails as it doesn't trust Elasticsearch's certificate.  
You need to figure out what is running on `/xxx.xxx.xxx.211:55756` and configure it to trust the certificate

---

<div class="post-metadata">

**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\
**Post date:** [January 29, 2020, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978/3 "2020-01-29T12:30:12Z")

</div>

Sorry, it was Metricbeat.

---

<div class="post-metadata">

**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\
**Post date:** [February 12, 2020, 9:27am UTC](https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978/4 "2020-02-12T09:27:54Z")

</div>

It was a certificate issue.

---

<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:** [March 11, 2020, 9:29am UTC](https://discuss.elastic.co/t/elasticsearch-https-secure-communication/216978/5 "2020-03-11T09:29:11Z")

</div>

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