# ERROR: Aborting enrolling to cluster. Could not communicate with the node on any of the addresses from the enrollment token. All of \[ip:9200\] were attempted
**URL:** https://discuss.elastic.co/t/error-aborting-enrolling-to-cluster-could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token-all-of-ip-9200-were-attempted/314651
**Category:** Elasticsearch
**Tags:** elastic-stack-security
**Created:** [September 18, 2022, 9:18pm UTC](https://discuss.elastic.co/t/error-aborting-enrolling-to-cluster-could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token-all-of-ip-9200-were-attempted/314651 "2022-09-18T21:18:05Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@hiruni.insyncit.net](https://discuss.elastic.co/u/hiruni.insyncit.net)
#### Post date: [September 18, 2022, 9:18pm UTC](https://discuss.elastic.co/t/error-aborting-enrolling-to-cluster-could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token-all-of-ip-9200-were-attempted/314651/1 "2022-09-18T21:18:05Z")
Hi,
I tried to join new node to existing Elastic cluster.
I'm using Elasticsearch version 8.4.1
Tried steps for new node:
1. sudo rpm --install elasticsearch-8.4.1-x86\_64.rpm
2. /usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token
I got this error at 2nd step.
Existing cluster (single node-cluster) configuration:
**node1**
cluster.name: my-application
node.name: node1
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
http.port: 9200
discovery.seed\_hosts: [" ip node1", "ip node2"]
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
xpack.security.http.ssl:
enabled: true
keystore.path: certs/http.p12
xpack.security.transport.ssl:
enabled: true
verification\_mode: certificate
keystore.path: certs/transport.p12
truststore.path: certs/transport.p12
cluster.initial\_master\_nodes: ["localhost.localdomain"]
http.host: 0.0.0.0
transport.host: 0.0.0.0
**New node configuration(node2):**
custer.name: my-application
node.name: node2
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
http.port: 9200
discovery.seed\_hosts: ["ip node1", "ip node2"]
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
xpack.security.http.ssl:
enabled: true
keystore.path: certs/http.p12
xpack.security.transport.ssl:
enabled: true
verification\_mode: certificate
keystore.path: certs/transport.p12
truststore.path: certs/transport.p12
cluster.initial\_master\_nodes: ["localhost.localdomain"]
http.host: 0.0.0.0
transport.host: 0.0.0.0
Error on **node2**
[root@localhost ~]# /usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token eyJ2ZXIiOiI4LjQuMSIsImFkciI6WyIxOTIuMTY4LjYwLjEzODo5MjAwIl0sImZnciI6ImQxOGU3NDYyZWI5MDM0OTJmMWM1MTYyOWUyNzhhODkzMTZhMDNmNGZjMWI1NWRiMWQ4ZDczNDEyNmZiMTViOTAiLCJrZXkiOiJZN3RMVW9NQlhhMTFibXNWWE5NQjpFNk9vUDY4OVNxU0xHRERVcDcwNjhRIn0=
This node will be reconfigured to join an existing cluster, using the enrollment token that you provided.
This operation will overwrite the existing configuration. Specifically:
- Security auto configuration will be removed from elasticsearch.yml
- The [certs] config directory will be removed
- Security auto configuration related secure settings will be removed from the elasticsearch.keystore
Do you want to continue with the reconfiguration process [y/N]y
Unable to communicate with the node on [https://ip](https://ip) node1:9200/\_security/enroll/node. Error was No route to host
ERROR: Aborting enrolling to cluster. Could not communicate with the node on any of the addresses from the enrollment token. All of [ip node1:9200] were attempted.
Thank You...!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 16, 2022, 9:18pm UTC](https://discuss.elastic.co/t/error-aborting-enrolling-to-cluster-could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token-all-of-ip-9200-were-attempted/314651/2 "2022-10-16T21:18:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.