# Kibana server is not ready yet

**URL:** <https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025>\
**Category:** Kibana\
**Created:** [November 16, 2018, 10:39am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025 "2018-11-16T10:39:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![subhas](https://avatars.discourse-cdn.com/v4/letter/s/ec9cab/32.png) [@subhas](https://discuss.elastic.co/u/subhas)\
**Post date:** [November 16, 2018, 10:39am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025/1 "2018-11-16T10:39:16Z")

</div>

Kibana url is not working. Whether kibana service is started or stopped, it is giving the same error when i go to [http://localhost:9243](http://localhost:9243) - "Kibana server is not ready yet". I am using centos 7. But the elasticsearch and kibana are on 6.5  
Thank you in advance.

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [November 16, 2018, 3:14pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025/2 "2018-11-16T15:14:11Z")

</div>

Hi

More info would be helpful, logs, screenshots console errors.

Can you please check the kibana server configuration in `kibana.yml` file? Have you defined the elasticserach node IP in `elasticserach.uri` under `kibana.yml` file?

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![subhas](https://avatars.discourse-cdn.com/v4/letter/s/ec9cab/32.png) [@subhas](https://discuss.elastic.co/u/subhas)\
**Post date:** [November 19, 2018, 9:13am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025/3 "2018-11-19T09:13:08Z")

</div>

Thank you Rashmi. Here is my kibana.xml  
server.port: 9243  
server.host: "0.0.0.0"  
elasticsearch.url: "[http://localhost:9200](http://localhost:9200)"

I get the below log whenever I restart kibana.

{"type":"log","@timestamp":"2018-11-19T09:12:11Z","tags":["info","migrations"],"pid":12004,"message":"Creating index .kibana\_2."}  
{"type":"log","@timestamp":"2018-11-19T09:12:11Z","tags":["warning","migrations"],"pid":12004,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana\_2 and restarting Kibana."}

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [November 19, 2018, 3:23pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025/4 "2018-11-19T15:23:23Z")

</div>

Are the ES logs available during this time? Ho w many nodes do you have ? Also try removing read-only from all indices:

`curl -X PUT http://localhost:9200/_all/_settings -H 'Content-Type: application/json' -d'{ "index.blocks.read_only_allow_delete" : false } }'`  
and check to see if Kibana finishes migrations.

There is a also a breaking change after an upgrade to 6.5, have you checked the release notes? ([https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0](https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0)).

Thanks  
Rashmi

---

<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:** [December 17, 2018, 3:23pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/157025/5 "2018-12-17T15:23:26Z")

</div>

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