Failed to determine the health of the cluster running

[111273 (อภิชาติ ปันแก้ว)]

Hi

I have error master_discovery_exception and change password bundle user.
Please have solution this case.

Elasticsearch.yml
cluster.name: rpa-Elasticsearch-test
http.port: 9200
node.data: true
node.master: true
node.name: RPA-AP2-T1.xxx
path.data: C:\ProgramData\Elastic\Elasticsearch\data
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs
xpack.license.self_generated.type: basic
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: rpa-Elasticsearch-t.xxx.p12
xpack.security.transport.ssl.truststore.path: rpa-Elasticsearch-t.xxx.p12
network.publish_host: RPA-AP2-T1.xxx
discovery.zen.ping.unicast.hosts: ["RPA-AP2-T1.xxx","RPA-AP2-T2.xxx","RPA-AP2-T3.xxx"]
cluster.initial_master_nodes: ["RPA-AP2-T1.xxx","RPA-AP2-T2.xxxx","RPA-AP2-T3.xxx"]
path.repo: ["C:\Program Files\Elastic\Elasticsearch\7.16.2\snapshot", "C:\Program Files\Elastic\Elasticsearch\7.16.2\backup"]
xpack.ml.enabled: false

Error
Failed to determine the health of the cluster running at http://xxx.xxx.xx.xxx:9200
it is recommented that you resolve the issues with your cluster before running Elasticsearch-setup-password.
it is very likely that the password changes will fail when run against an unhealthy cluster.

[warkolm (Mark Walkom)]

Please don't post pictures of text, logs or code. They are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them