# SSL between elastic nodes is failing

**URL:** <https://discuss.elastic.co/t/ssl-between-elastic-nodes-is-failing/91925>\
**Category:** Elasticsearch\
**Created:** [July 5, 2017, 2:28pm UTC](https://discuss.elastic.co/t/ssl-between-elastic-nodes-is-failing/91925 "2017-07-05T14:28:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [July 6, 2017, 4:03am UTC](https://discuss.elastic.co/t/ssl-between-elastic-nodes-is-failing/91925/2 "2017-07-06T04:03:43Z")

</div>

You are running into this issue from the [Setting up SSL/TLS](https://www.elastic.co/guide/en/x-pack/5.4/ssl-tls.html#installing-node-certificates) documentation:

> If you choose not to use the certgen, the certificates that you obtain must allow for both clientAuth and serverAuth if the extended key usage extension is present.

SSL certificates _can_ be marked (but don't have to be) as allowing either "client authentication" or "server authentication" or both. Because there is no strict notion of "client" or "server" in a cluster (all nodes act as both a client and a server) your certificate must either be marked as having _both_ `clientAuth` and `serverAuth` _extended key usage_, or not have that extension included at all.

You'll need to generate new certificates.

---

_[View the full topic](https://discuss.elastic.co/t/ssl-between-elastic-nodes-is-failing/91925)._
