# Issues will configure xpack in cluster

**URL:** <https://discuss.elastic.co/t/issues-will-configure-xpack-in-cluster/192122>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [July 24, 2019, 7:21pm UTC](https://discuss.elastic.co/t/issues-will-configure-xpack-in-cluster/192122 "2019-07-24T19:21:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cbeprem](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@cbeprem](https://discuss.elastic.co/u/cbeprem)\
**Post date:** [July 24, 2019, 7:21pm UTC](https://discuss.elastic.co/t/issues-will-configure-xpack-in-cluster/192122/1 "2019-07-24T19:21:02Z")

</div>

Hi Team,

I am trying to configure a new cluster . it worked fine. before i try to configure xpack. I have followed this article [https://www.elastic.co/blog/getting-started-with-elasticsearch-security](https://www.elastic.co/blog/getting-started-with-elasticsearch-security)  
If i disable xpack in elasticsearch.yml. it works fine . Elastic search is starting but not able to get localhost:9200 i am not able to generate password. Below is the error of elastic search logs

> **[2019-07-25\_0022](https://www.screencast.com/t/CowWVw6cmE)**
>
> Shared from Screencast.com

Kindly guide me .

Regards,  
Prem.

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [July 25, 2019, 3:59am UTC](https://discuss.elastic.co/t/issues-will-configure-xpack-in-cluster/192122/2 "2019-07-25T03:59:51Z")

</div>

Please do not post screenshots of logs. Many people read these forums over email or on mobile devices where screenshots are difficult to read.

The message in your logs is not the cause of your problem.

> [@cbeprem](#):
>
> Elastic search is starting but not able to get localhost:9200

What happens whe you try to connect to localhost over curl?  
What does your `elasticsearch.yml` look like?

---

<div class="post-metadata">

**Author:** ![cbeprem](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@cbeprem](https://discuss.elastic.co/u/cbeprem)\
**Post date:** [July 29, 2019, 6:09pm UTC](https://discuss.elastic.co/t/issues-will-configure-xpack-in-cluster/192122/3 "2019-07-29T18:09:28Z")

</div>

Hi Tim,

Here is the output of curl

[root@ elasticsearch]# curl [http://1:9200](http://1:9200)  
{"error":{"root\_cause":[{"type":"security\_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}}],"type":"security\_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}},"status":401}

and here is the config elasticsearch.yml

xpack.security.enabled: true  
xpack.security.transport.ssl.enabled: true  
xpack.security.transport.ssl.verification\_mode: full  
xpack.security.transport.ssl.keystore.path: premelastciclustermaster-01.p12  
xpack.security.transport.ssl.truststore.path: premelastciclustermaster-01.p12

[root@premtestclustermaster elasticsearch]# bin/elasticsearch-setup-passwords auto

Failed to authenticate user 'elastic' against http://:9200/\_security/\_authenticate?pretty  
Possible causes include:

- The password for the 'elastic' user has already been changed on this cluster
- Your elasticsearch node is running against a different keystore  
This tool used the keystore at /etc/elasticsearch/elasticsearch.keystore

ERROR: Failed to verify bootstrap password

Kindly help me solve this issue.

Regards,  
Prem.

---

<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:** [August 26, 2019, 6:09pm UTC](https://discuss.elastic.co/t/issues-will-configure-xpack-in-cluster/192122/4 "2019-08-26T18:09:29Z")

</div>

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