# Kibana server is not ready yet \[self-managed\]

**URL:** <https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-self-managed/271734>\
**Category:** Kibana\
**Created:** [April 30, 2021, 3:09am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-self-managed/271734 "2021-04-30T03:09:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dylawn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dylawn/32/87974_2.png) [@Dylawn](https://discuss.elastic.co/u/Dylawn)\
**Post date:** [April 30, 2021, 3:09am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-self-managed/271734/1 "2021-04-30T03:09:12Z")

</div>

Running these services on one self-hosted Ubuntu VM on Google:

- elasticsearch - not yet setup to be accessible externally
- enterprise-search - accessible externally
- kibana - **should be accessible externally but something is wrong!**

I can access enterprise-search from the public url.  
I have almost identical firewall rules for enterprise-search and kibana except for the name and port number.

`$ sudo journalctl -fu kibana.service`

```auto
Apr 30 02:56:34 webserver-1 systemd[1]: Stopped Kibana.
Apr 30 02:56:34 webserver-1 systemd[1]: Started Kibana.

```

Visiting `http://<public_url>:5601/` shows only `Kibana server is not ready yet`.

kibana.yml:

```auto
server.port: 5601
server.host: 192.168.2.3
server.publicBaseUrl: "http://<public_url>:5601/"

```

elasticsearch.yml:

```auto
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml*
xpack.security.enabled: true
xpack.security.authc.api_key.enabled: true

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 30, 2021, 4:15am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-self-managed/271734/2 "2021-04-30T04:15:41Z")

</div>

Welcome to our community! 😃

What do your Kibana logs show?

---

<div class="post-metadata">

**Author:** ![Dylawn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dylawn/32/87974_2.png) [@Dylawn](https://discuss.elastic.co/u/Dylawn)\
**Post date:** [April 30, 2021, 6:42pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-self-managed/271734/3 "2021-04-30T18:42:55Z")

</div>

Thank you!

Found logs with:  
`tail -f /var/log/kibana/kibana.log`

Saw:  
`License information could not be obtained from Elasticsearch due to [security_exception] missing authentication credentials for REST request`

Updated:  
`/etc/kibana/kibana.yml`  
and added:

```auto
elasticsearch.username: "kibana_system"
elasticsearch.password: "<pass>"

```

It's working!

---

<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:** [May 28, 2021, 6:43pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-self-managed/271734/4 "2021-05-28T18:43:02Z")

</div>

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