# ERROR: Skipping security auto configuration because it appears that the node is not starting up for the first time. The node might already be part of a cluster and this auto setup utility is designed to configure Security for new clusters only., with exit

**URL:** <https://discuss.elastic.co/t/error-skipping-security-auto-configuration-because-it-appears-that-the-node-is-not-starting-up-for-the-first-time-the-node-might-already-be-part-of-a-cluster-and-this-auto-setup-utility-is-designed-to-configure-security-for-new-clusters-only-with-exit/344422>\
**Category:** Elasticsearch\
**Created:** [October 4, 2023, 6:29pm UTC](https://discuss.elastic.co/t/error-skipping-security-auto-configuration-because-it-appears-that-the-node-is-not-starting-up-for-the-first-time-the-node-might-already-be-part-of-a-cluster-and-this-auto-setup-utility-is-designed-to-configure-security-for-new-clusters-only-with-exit/344422 "2023-10-04T18:29:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nav\_11](https://avatars.discourse-cdn.com/v4/letter/n/8edcca/32.png) [@nav\_11](https://discuss.elastic.co/u/nav_11)\
**Post date:** [October 4, 2023, 6:29pm UTC](https://discuss.elastic.co/t/error-skipping-security-auto-configuration-because-it-appears-that-the-node-is-not-starting-up-for-the-first-time-the-node-might-already-be-part-of-a-cluster-and-this-auto-setup-utility-is-designed-to-configure-security-for-new-clusters-only-with-exit/344422/1 "2023-10-04T18:29:24Z")

</div>

Getting below error while adding the node. I am following the MACOS setup guide below.

> **[Install Elasticsearch from archive on Linux or MacOS | Elasticsearch Guide...](https://www.elastic.co/guide/en/elasticsearch/reference/master/targz.html)**

Command: bin/elasticsearch --enrollment-token

ERROR: Skipping security auto configuration because it appears that the node is not starting up for the first time. The node might already be part of a cluster and this auto setup utility is designed to configure Security for new clusters only., with exit code 80

Checked the below doc and need more understanding on how to delete the Elasticsearch dir on the second node. How to find the where the dir is created for the second node. Also what needs to be done after this step. Appreciate your prompt help.

> [@Node Auto Configuration](https://discuss.elastic.co/t/node-auto-configuration/297543):
>
> Hi there, I´m trying to deploy a new cluster using Elasticsearch 8 but it seens that is not working the way I expected. 4 Servers: 3 Elasticsearch 1 kibana All in the same network. I´m following the steps using the Elasticsearch website to add new nodes which is: bin/elasticsearch-create-enrollment-token -s node After created the token, I´m trying to add the second node(server) using: bin/elasticsearch --enrollment-token \<enrollment-token\> After that, I´m receiving the following error…

---

<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:** [November 1, 2023, 6:30pm UTC](https://discuss.elastic.co/t/error-skipping-security-auto-configuration-because-it-appears-that-the-node-is-not-starting-up-for-the-first-time-the-node-might-already-be-part-of-a-cluster-and-this-auto-setup-utility-is-designed-to-configure-security-for-new-clusters-only-with-exit/344422/2 "2023-11-01T18:30:23Z")

</div>

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