# SSL issue when node tries connection to master in elasticsearch cluster-SOLVED

**URL:** <https://discuss.elastic.co/t/ssl-issue-when-node-tries-connection-to-master-in-elasticsearch-cluster-solved/174431>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [March 28, 2019, 9:07pm UTC](https://discuss.elastic.co/t/ssl-issue-when-node-tries-connection-to-master-in-elasticsearch-cluster-solved/174431 "2019-03-28T21:07:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dragan979](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dragan979/32/42739_2.png) [@dragan979](https://discuss.elastic.co/u/dragan979)\
**Post date:** [March 28, 2019, 9:07pm UTC](https://discuss.elastic.co/t/ssl-issue-when-node-tries-connection-to-master-in-elasticsearch-cluster-solved/174431/1 "2019-03-28T21:07:33Z")

</div>

I used SearchGuard to encrypt nodes in ElasticSearch cluster

Master:

```
cluster.name: client1
searchguard.enterprise_modules_enabled: false

 
node.name: ekl.test.com
node.master: true
node.data: true
node.ingest: true

network.host: 0.0.0.0

#http.host: 0.0.0.0
network.publish_host: ["ekl1.test1.com","ekl.test.com"]

 
http.port: 9200
 

discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]

 
discovery.zen.minimum_master_nodes: 1
 
xpack.security.enabled: false

searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node1.pem'
searchguard.ssl.transport.pemkey_filepath: 'ssl/node1.key'
searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.ssl.transport.enforce_hostname_verification: false
searchguard.ssl.transport.resolve_hostname: false
searchguard.ssl.http.enabled: true
searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node1_http.pem'
searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node1_http.key'
searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.nodes_dn:
- CN=ekl.test.com,OU=Ops,O=BugBear BG\, Ltd.,DC=BugBear,DC=com
- CN=ekl1,test1.com,OU=Ops,O=BugBear BG\, Ltd.,DC=BugBear,DC=com
searchguard.authcz.admin_dn:
- CN=admin.test.com,OU=Ops,O=BugBear Com\, Inc.,DC=example,DC=com

```

Node:

```
cluster.name: client1
searchguard.enterprise_modules_enabled: false

 
node.name: ekl1.test.com
node.master: false
node.data: true
node.ingest: false

network.host: 0.0.0.0

#http.host: 0.0.0.0
network.publish_host: ["ekl1.test1.com","ekl.test.com"]

 
http.port: 9200
 

discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]

 
discovery.zen.minimum_master_nodes: 1
 
xpack.security.enabled: false

searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node2.pem'
searchguard.ssl.transport.pemkey_filepath: 'ssl/node2.key'
searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.ssl.transport.enforce_hostname_verification: false
searchguard.ssl.transport.resolve_hostname: false
searchguard.ssl.http.enabled: true
searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node2_http.pem'
searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node2_http.key'
searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.nodes_dn:
- CN=ekl.test.com,OU=Ops,O=BugBear BG\, Ltd.,DC=BugBear,DC=com
- CN=ekl1.test1.com,OU=Ops,O=BugBear BG\, Ltd.,DC=BugBear,DC=com
searchguard.authcz.admin_dn:
- CN=admin.test.com,OU=Ops,O=BugBear Com\, Inc.,DC=example,DC=com

```

Certificates are self-signed

From node i can telnet to ports 9200/9300 by hostnames

curl -kvX GET "[https://admin:pass@ekl.test.com:9200](https://admin:pass@ekl.test.com:9200)" works fine

Errors on node:

[[ekl1.test1.com](http://ekl1.test1.com)] not enough master nodes discovered during pinging (found [], but needed [1]), pinging again  
ES Config path is /etc/elasticsearch [2019-03-28T21:25:56,450][INFO][c.f.s.s.DefaultSearchGuardKeyStore] \>[[ekl1.test1.com](http://ekl1.test1.com)] OpenSSL not available (this is not an error, we simply \>fallback to built-in JDK SSL) because of java.lang.ClassNotFoundException: \>io.netty.internal.tcnative.SSL

Both server names are correct

---

<div class="post-metadata">

**Author:** ![dragan979](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dragan979/32/42739_2.png) [@dragan979](https://discuss.elastic.co/u/dragan979)\
**Post date:** [March 29, 2019, 6:03am UTC](https://discuss.elastic.co/t/ssl-issue-when-node-tries-connection-to-master-in-elasticsearch-cluster-solved/174431/2 "2019-03-29T06:03:38Z")

</div>

Solved by adding transport.network: [ekl1.test1.com](http://ekl1.test1.com) in node file

---

<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:** [April 26, 2019, 6:03am UTC](https://discuss.elastic.co/t/ssl-issue-when-node-tries-connection-to-master-in-elasticsearch-cluster-solved/174431/3 "2019-04-26T06:03:52Z")

</div>

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