# Can't add a new node to an es cluster with x-pack:enabled **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [January 12, 2021, 4:01pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862 "2021-01-12T16:01:57Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![KaZuKi\_Yashiro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kazuki_yashiro/32/80467_2.png) [@KaZuKi\_Yashiro](https://discuss.elastic.co/u/KaZuKi_Yashiro)\ **Post date:** [January 12, 2021, 4:01pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862/1 "2021-01-12T16:01:58Z")
I need to transfer the elasticsearch cluster from two servers to another two servers, without downtime or restart. How can this be done? I've tried to add a new node to an existing cluster with x-pack, but it doesn't work. **elasticsearch.yml from an existing cluster:** > cluster.name: test1 > discovery.zen.minimum\_master\_nodes: 2 > discovery.zen.ping.unicast.hosts: > - 192.168.0.200 > - 192.168.0.228 > network.host: 192.168.0.228 > network.publish\_host: 192.168.0.228 > node.name: node1 > transport.tcp.port: 11300 > xpack.security.enabled: true > xpack.security.http.ssl.enabled: false > xpack.security.transport.ssl.enabled: false > xpack.monitoring.enabled: false I try to up a new node: **elasticsearch.yml new node:** > cluster.name: test1 > discovery.zen.minimum\_master\_nodes: 2 > discovery.zen.ping.unicast.hosts: > - 192.168.0.200 > - 192.168.0.228 > - 192.168.0.201 > network.host: 192.168.0.201 > network.publish\_host: 192.168.0.201 > node.name: node3 > transport.tcp.port: 11300 > xpack.security.enabled: true > xpack.security.http.ssl.enabled: false > xpack.security.transport.ssl.enabled: false > xpack.monitoring.enabled: false **And it's an error:** `[INFO][o.e.d.z.ZenDiscovery] [host_es3] failed to send join request to master [{hosts_es1}{DQ1ykmejSdGT82uguq5-Eg}{SMAVCMVeST6uehYnhgdmUQ}{192.168.0.228}{192.168.0.228:11300}{ml.machine_memory=17179869184, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}], reason [RemoteTransportException[[hosts_es1][172.17.0.8:11300][internal:discovery/zen/join]]; nested: IllegalStateException[Transport TLS ([xpack.security.transport.ssl.enabled]) is required for license type [basic] when security is enabled]; ]` **P.S.** xpack.security.http.ssl.enabled/xpack.security.transport.ssl.enabled - false, because we don't use them 🙂 ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 12, 2021, 4:34pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862/2 "2021-01-12T16:34:02Z")
What versions are all your nodes? I think you're using different versions for the new nodes, and this problem would go away if you used the same version everywhere. ---
**Author:** ![KaZuKi\_Yashiro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kazuki_yashiro/32/80467_2.png) [@KaZuKi\_Yashiro](https://discuss.elastic.co/u/KaZuKi_Yashiro)\ **Post date:** [January 12, 2021, 5:24pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862/3 "2021-01-12T17:24:38Z")
> [@DavidTurner](#): > > What versions are all your nodes? I think you're using different versions for the new nodes, and this problem would go away if you used the same version everywhere. Version 6.8.8 everywhere ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 12, 2021, 5:41pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862/4 "2021-01-12T17:41:20Z")
Ok, in which case you're not allowed to set `xpack.security.transport.ssl.enabled: false`. Transport TLS is required when `xpack.security.enabled: true`. I think this works by accident for your original two nodes, but it'd stop working if you restarted one of them and not the other. ---
**Author:** ![KaZuKi\_Yashiro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kazuki_yashiro/32/80467_2.png) [@KaZuKi\_Yashiro](https://discuss.elastic.co/u/KaZuKi_Yashiro)\ **Post date:** [January 14, 2021, 3:04pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862/5 "2021-01-14T15:04:43Z")
Ok, got it. Thanks a lot! After enabling `xpack.security.transport.ssl.enabled` and add SSL certificates - it's works. 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 11, 2021, 3:04pm UTC](https://discuss.elastic.co/t/cant-add-a-new-node-to-an-es-cluster-with-x-pack-enabled/260862/6 "2021-02-11T15:04:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.