# X-pack Failed to authenticate user \[elastic\] **URL:** \ **Category:** Elasticsearch\ **Created:** [March 30, 2018, 4:59am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179 "2018-03-30T04:59:07Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![f26227279](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/f26227279/32/21296_2.png) [@f26227279](https://discuss.elastic.co/u/f26227279)\ **Post date:** [March 30, 2018, 4:59am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/1 "2018-03-30T04:59:07Z")
Hi everyone, after installing x-pack, I know I need to modify the elasticsearch password.But when I use the command on ES `bin/x-pack/setup-passwords interactive` it show me an error: ``` Failed to authenticate user 'elastic' against http://172.30.254.23:9200/_xpack/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 /home/es2/Downloads/elasticsearch-6.2.2/config/elasticsearch.keystore ERROR: Failed to verify bootstrap password ``` ES log: `[ES2] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]` so now I can't log in to ES because I don't know the default password and even can't modify the password. this is my ES config: ``` # ======================== Elasticsearch Configuration ========================= # # NOTE: Elasticsearch comes with reasonable defaults for most settings. # Before you set out to tweak and tune the configuration, make sure you # understand what are you trying to accomplish and the consequences. # # The primary way of configuring a node is via this file. This template lists # the most important settings you may want to configure for a production cluster. # # Please consult the documentation for further information on configuration options: # https://www.elastic.co/guide/en/elasticsearch/reference/index.html # # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # cluster.name: Winoc # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # node.name: ES2 # # Add custom attributes to the node: # #node.attr.rack: r1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # #path.data: /path/to/data # # Path to log files: # #path.logs: /path/to/logs # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # #bootstrap.memory_lock: true # #bootstrap.memory_lock: true # # Make sure that the heap size is set to about half the memory available # on the system and that the owner of the process is allowed to use this # limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # Set the bind address to a specific IP (IPv4 or IPv6): # network.host: 172.30.254.23 # # Set a custom port for HTTP: # #http.port: 9200 # # For more information, consult the network module documentation. # # --------------------------------- Discovery ---------------------------------- # # Pass an initial list of hosts to perform discovery when new node is started: # The default list of hosts is ["127.0.0.1", "[::1]"] # #discovery.zen.ping.unicast.hosts: ["172.30.254.23", "172.30.254.24", "172.30.254.27", "172.30.254.28"] # # Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1): # #discovery.zen.minimum_master_nodes: # # For more information, consult the zen discovery module documentation. # # ---------------------------------- Gateway ----------------------------------- # # Block initial recovery after a full cluster restart until N nodes are started: # #gateway.recover_after_nodes: 3 # # For more information, consult the gateway module documentation. # # ---------------------------------- Various ----------------------------------- # Require explicit names when deleting indices: # #action.destructive_requires_name: true xpack.security.audit.enabled: "true" #elasticsearch.username: "" ``` thank you in advance! ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [March 30, 2018, 5:37am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/2 "2018-03-30T05:37:17Z")
Hi, Your `elasticsearch.yml` says Elasticsearch is listening on `network.host: 172.30.254.23` and `setup-passwords` ran against `172.30.214.21` which means that you either - Ran `setup-passwords` with a `--url` argument - Ran `setup-passwords` from a different node - Ran `setup-passwords` using a different `$ES_CONF_PATH` - Haven't restarted Elasticsearch after making changes to your `elasticsearch.yml` - made changes to the elasticsearch.yml file you copied here after running `setup-passwords` Can you clarify? Also, have you run `setup-passwords` before successfully before getting that error ? Does elasticsearch start without any errors in the log ? ---
**Author:** ![Krunal\_kalaria](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krunal_kalaria/32/23862_2.png) [@Krunal\_kalaria](https://discuss.elastic.co/u/Krunal_kalaria)\ **Post date:** [March 30, 2018, 5:37am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/3 "2018-03-30T05:37:35Z")
Hi @f26227279, Can you check the elasticsearch service is start or not and try this command to show the password: bin/x-pack/setup-passwords auto -u "[http://172.30.214.21:9200](http://172.30.214.21:9200)" Thanks & Regards, Krunal. ---
**Author:** ![f26227279](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/f26227279/32/21296_2.png) [@f26227279](https://discuss.elastic.co/u/f26227279)\ **Post date:** [March 30, 2018, 5:42am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/4 "2018-03-30T05:42:56Z")
I am very sorry for that I modify the ip because I am afraid of being invaded, now I have modified it to correct ip! bin/x-pack/setup-passwords auto -u "[http://172.30.254.23:9200](http://172.30.254.23:9200)" has the same problem: ``` Failed to authenticate user 'elastic' against http://172.30.254.23:9200/_xpack/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 /home/es2/Downloads/elasticsearch-6.2.2/config/elasticsearch.keystore ERROR: Failed to verify bootstrap password ``` ---
**Author:** ![f26227279](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/f26227279/32/21296_2.png) [@f26227279](https://discuss.elastic.co/u/f26227279)\ **Post date:** [March 30, 2018, 5:43am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/5 "2018-03-30T05:43:56Z")
yes, I have ever success on one node, but when I set the seccond node, it has the error. on the second node `setup-passwords` never success. ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [March 30, 2018, 5:54am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/6 "2018-03-30T05:54:18Z")
You don't have to re run `setup-password` on each node of the same cluster. Can you not authenticate user elastic with the password you set the first time you ran the `setup-password` ? ---
**Author:** ![f26227279](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/f26227279/32/21296_2.png) [@f26227279](https://discuss.elastic.co/u/f26227279)\ **Post date:** [March 30, 2018, 6:55am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/7 "2018-03-30T06:55:45Z")
I can't use the first time password I set to log in. ``` [root@10-255-254-23 elasticsearch-6.2.2]# curl -u elastic 'http://172.30.254.23:9200/_xpack/security/_authenticate?pretty' Enter host password for user 'elastic': { "error" : { "root_cause" : [ { "type" : "security_exception", "reason" : "failed to authenticate user [elastic]", "header" : { "WWW-Authenticate" : "Basic realm=\"security\" charset=\"UTF-8\"" } } ], "type" : "security_exception", "reason" : "failed to authenticate user [elastic]", "header" : { "WWW-Authenticate" : "Basic realm=\"security\" charset=\"UTF-8\"" } }, "status" : 401 } ``` but on third node, I can log in using first password I set. ---
**Author:** ![f26227279](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/f26227279/32/21296_2.png) [@f26227279](https://discuss.elastic.co/u/f26227279)\ **Post date:** [March 30, 2018, 7:28am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/8 "2018-03-30T07:28:54Z")
it works! after open the `discovery.zen.ping.unicast.hosts` thank you very much 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 27, 2018, 7:29am UTC](https://discuss.elastic.co/t/x-pack-failed-to-authenticate-user-elastic/126179/9 "2018-04-27T07:29:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.