# Could not communicate with the node on any of the addresses from the enrollment token
**URL:** https://discuss.elastic.co/t/could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token/369927
**Category:** Elasticsearch
**Tags:** elastic-stack-security
**Created:** [November 2, 2024, 1:09am UTC](https://discuss.elastic.co/t/could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token/369927 "2024-11-02T01:09:39Z")
**Posts on this page:** 1
**Page:** 1
### Author:  [@germebl](https://discuss.elastic.co/u/germebl)
#### Post date: [November 2, 2024, 1:09am UTC](https://discuss.elastic.co/t/could-not-communicate-with-the-node-on-any-of-the-addresses-from-the-enrollment-token/369927/1 "2024-11-02T01:09:39Z")
Hey everyone,
actually doing my very first steps with elastic and want to use it with the full ELK Stack. I decided for a testing cluster of 3 elastic nodes and one kibana nodes.
The node-1 is running fine with this elasticsearch.yaml changes:
```auto
cluster.name: elk-cluster
node.name: elk1
path.data: /mnt/elk1-data
bootstrap.memory_lock: true
network.host: 10.1.201.7
transport.host: 0.0.0.0
```
The other nodes running with something like:
```auto
cluster.name: elk-cluster
node.name: elk2
path.data: /mnt/elk2-data
network.host: 10.1.201.8
bootstrap.memory_lock: true
```
Surely i've set the limits.conf to unlimited for elasticsearch memlock, changed LimitMEMLOCK to infinity in the systemd file. The JVM options are set to 50% of cpu. I've reloaded the systemd daemon after the changes on systemd.
I've generated a enrollment token on `node-1` and posted it to `node-2` as following command:
```auto
/usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token
```
The error message shows:
```auto
Unable to communicate with the node on https://10.1.201.7:9200/_security/enroll/node. Error was null
ERROR: Aborting enrolling to cluster. Could not communicate with the node on any of the addresses from the enrollment token. All of [10.1.201.7:9200] were attempted., with exit code 69
```
When checking the cluster log of 10.1.201.7 i cant find anything interesting else this:
```auto
[2024-11-02T00:48:29,189][WARN][o.e.c.c.ClusterBootstrapService] [elk1] this node is locked into cluster UUID [DsT9lOc6RMml4uPZ5LWgvg] but [cluster.initial_master_nodes] is set to [elk1]; remove this setting to avoid possible data loss caused by subsequent cluster bootstrap attempts; for further information see https://www.elastic.co/guide/en/elasticsearch/reference/8.15/important-settings.html#initial_master_nodes
```
When doing a curl from `node-2` to `node-1` it works fine:
```auto
curl -k -u elastic: 'https://10.1.201.7:9200/_cluster/health?pretty'
```
Any idea what i'm doing wrong? Would like every hint.
//Edit
I dont know if its important...I tried multiple times multilple ways. But everytime i purged elasticsearch (`apt purge elasticsearch`) and took sure that the directorys (`data dir, conf dir`) are deleted.
Best regards