# Cerificate error

**URL:** <https://forum.opensearch.org/t/cerificate-error/276>\
**Category:** Open Source Elasticsearch and Kibana\
**Created:** [March 27, 2019, 11:25am UTC](https://forum.opensearch.org/t/cerificate-error/276 "2019-03-27T11:25:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nishant](https://avatars.discourse-cdn.com/v4/letter/n/53a042/32.png) [@Nishant](https://forum.opensearch.org/u/Nishant)\
**Post date:** [March 27, 2019, 11:25am UTC](https://forum.opensearch.org/t/cerificate-error/276/1 "2019-03-27T11:25:48Z")

</div>

I have a single host on which 3 ES node cluster is running using Docker. Out of these 3 nodes, 2 nodes are master-eligible node and one is data node. So the two master-eligible nodes are sharing a common elasticsearch.yml file and data node has different elasticsearch.yml file. So far I have configured the SSL/TLS certificate for the node but I haven’t changed the admin certificate, it is using the default one that is

```
opendistro_security.authcz.admin_dn:
  - CN=admin,OU=SSL,O=Test,L=Test,C=DE

```

I am getting this error whenever I start my docker container of ES:

```
[2019-03-27T11:02:59,622][ERROR][c.a.o.s.t.OpenDistroSecurityRequestHandler] [elsatic-node-1] ElasticsearchException[Illegal parameter in http or transport request found.

This means that one node is trying to connect to another with 

a non-node certificate (no OID or opendistro_security.nodes_dn incorrect configured) or that someone 

is spoofing requests. Check your TLS certificate setup as described in documentation]

```

How can I resolve this issue?

P.S: Wildcard certificate is being used for configuring the node certificates.

---

<div class="post-metadata">

**Author:** ![Nishant](https://avatars.discourse-cdn.com/v4/letter/n/53a042/32.png) [@Nishant](https://forum.opensearch.org/u/Nishant)\
**Post date:** [April 3, 2019, 4:40pm UTC](https://forum.opensearch.org/t/cerificate-error/276/2 "2019-04-03T16:40:40Z")

</div>

Check [Nodes\_dn configuration - #3 by Nishant](https://forum.opensearch.org/t/nodes-dn-configuration/313/3)

---

<div class="post-metadata">

**Author:** ![kwslavens](https://avatars.discourse-cdn.com/v4/letter/k/d78d45/32.png) [@kwslavens](https://forum.opensearch.org/u/kwslavens)\
**Post date:** [April 5, 2019, 6:01pm UTC](https://forum.opensearch.org/t/cerificate-error/276/3 "2019-04-05T18:01:56Z")

</div>

I have run into this issue also. I found the solution by looking at Search Guards TLS documentation.

> **[Configuring TLS](https://docs.search-guard.com/latest/configuring-tls)**
>
> Search Guard TLS configuration settings for the REST and the transport layer. Extended security options for hostname verification and DNS lookups.

You have to either list all the nodes by DN on each server. Or your certificates have to have the same OID key.

```auto
searchguard.nodes_dn:
  - 'CN=node.other.com,OU=SSL,O=Test,L=Test,C=DE'
  - 'CN=*.example.com,OU=SSL,O=Test,L=Test,C=DE'
  - 'CN=elk-devcluster*'
  - '/CN=.*regex/'

```

I ended up using the Search Guard offline TLS Tool.

> **[Offline TLS Tool](https://docs.search-guard.com/latest/offline-tls-tool)**
>
> Use the Search Guard TLS tool to generate production-ready TLS certificates for your Elasticsearch cluster.

This let me create a CA all my node certs and admin certs at the same time. I also noticed in its docs an option to set admin certs to also include an admin tag. “admin: true”. This may or may not matter.

---

<div class="post-metadata">

**Author:** ![gude.ravi](https://avatars.discourse-cdn.com/v4/letter/g/73ab20/32.png) [@gude.ravi](https://forum.opensearch.org/u/gude.ravi)\
**Post date:** [August 11, 2019, 1:54pm UTC](https://forum.opensearch.org/t/cerificate-error/276/4 "2019-08-11T13:54:33Z")

</div>

I am running into the same issue with self signed certs. Can you please share an example tlsconfig that you used for your cluster ?
