# After enabling xpack.security.enabled: true in elasticsearch kibana url is saying kibana server is not ready

**URL:** <https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring, elastic-stack-security\
**Created:** [September 22, 2020, 8:12am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474 "2020-09-22T08:12:20Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![praveencdcx](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@praveencdcx](https://discuss.elastic.co/u/praveencdcx)\
**Post date:** [September 22, 2020, 8:12am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/1 "2020-09-22T08:12:20Z")

</div>

Hello, I am using basic version of Elastic and kibana 7.9. after configuration am not able to see Users and roles tab under stack-management. so tried enabling xpack in elasticsearch.yml file.after enabling and starting elasticsearch service. Kibana url is not loading getting "Kiabana server is not ready.

---

<div class="post-metadata">

**Author:** ![chandu5565](https://avatars.discourse-cdn.com/v4/letter/c/c57346/32.png) [@chandu5565](https://discuss.elastic.co/u/chandu5565)\
**Post date:** [September 22, 2020, 8:52am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/2 "2020-09-22T08:52:45Z")

</div>

It might be due to communication encryption between elasticsearch and kibana.

You can see the logs of kibana for detailed error.

By enabling http & ssl encryption on elasticsearch this can be resolved.

---

<div class="post-metadata">

**Author:** ![praveencdcx](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@praveencdcx](https://discuss.elastic.co/u/praveencdcx)\
**Post date:** [September 22, 2020, 9:42am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/3 "2020-09-22T09:42:06Z")

</div>

Hi, I dont see any kibana.log is created under /var/log/.. in kibana.yml file i see logging.dest: stdout as log destination..where i can find logs if it mention like this.

Also, can you please let me know what parameter i have to update in elasticsearch.yml for http enablement.

If i update logging.dest:/var/log/kibana.log kibana service is not restarting.

---

<div class="post-metadata">

**Author:** ![kavierkoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavierkoo/32/86555_2.png) [@kavierkoo](https://discuss.elastic.co/u/kavierkoo)\
**Post date:** [September 22, 2020, 10:15am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/4 "2020-09-22T10:15:44Z")

</div>

You can see the logs by running `journalctl -xe`

---

<div class="post-metadata">

**Author:** ![praveencdcx](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@praveencdcx](https://discuss.elastic.co/u/praveencdcx)\
**Post date:** [September 22, 2020, 11:50am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/5 "2020-09-22T11:50:21Z")

</div>

I have enabled xpack.security.enabled: true and xpack.security.transport.ssl.enabled: true in elasticsearch.yaml and restarted service. now kibana is showing "Kibana server is not ready yet",but kibana service is running.

Logs from elasticsearch.log  
[2020-09-22T13:43:38,254][INFO][o.e.x.s.a.AuthenticationService] [el9512] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]  
[2020-09-22T13:43:40,776][INFO][o.e.x.s.a.AuthenticationService] [el9512] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

But kibana service is running.  
● kibana.service - Kibana  
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)  
Active: active (running) since Tue 2020-09-22 13:41:12 CEST; 14min ago  
Main PID: 87611 (node)  
CGroup: /system.slice/kibana.service  
└─87611 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli

---

<div class="post-metadata">

**Author:** ![chandu5565](https://avatars.discourse-cdn.com/v4/letter/c/c57346/32.png) [@chandu5565](https://discuss.elastic.co/u/chandu5565)\
**Post date:** [September 23, 2020, 6:05am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/6 "2020-09-23T06:05:09Z")

</div>

Did you run the below command to set-up users and passwords.

/usr/share/elasticsearch/bin/elasticsearch-setup-passwords interactive

if not run the above command and set the passwords. later add the username and password to kibana.yml

---

<div class="post-metadata">

**Author:** ![praveencdcx](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@praveencdcx](https://discuss.elastic.co/u/praveencdcx)\
**Post date:** [September 23, 2020, 7:55am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/7 "2020-09-23T07:55:12Z")

</div>

Perfect !! It worked as expected.. Thanks a lot !!

---

<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:** [October 21, 2020, 7:55am UTC](https://discuss.elastic.co/t/after-enabling-xpack-security-enabled-true-in-elasticsearch-kibana-url-is-saying-kibana-server-is-not-ready/249474/8 "2020-10-21T07:55:18Z")

</div>

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