# Kibana is stock on “Kibana server is not ready yet”

**URL:** <https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021>\
**Category:** Kibana\
**Created:** [November 11, 2020, 8:16am UTC](https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021 "2020-11-11T08:16:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hadi\_farzipour](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hadi_farzipour/32/69187_2.png) [@hadi\_farzipour](https://discuss.elastic.co/u/hadi_farzipour)\
**Post date:** [November 11, 2020, 8:16am UTC](https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021/1 "2020-11-11T08:16:27Z")

</div>

Hi everyone

After installing Inhanced-Table plugin, my Kibana is stock on following message

```auto
  "Kibana server is not ready yet"

```

However after some minutes it completely became out of reach and I face with "Unable to connect" error on my browser.

I removed the plugin with following command but the error still exists.

./bin/kibana-plugin remove enhanced-table

Would you mind helping me in order to solve this problem. Also Kibana logfile is available via following link.

> **[kibana.log](https://drive.google.com/file/d/1LILdo07Q9r0-VNG7hgkbTOaE2eJzhQPs/view?usp=sharing)**
>
> Google Drive file.

Thanks Best Regards

---

<div class="post-metadata">

**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\
**Post date:** [November 11, 2020, 10:34am UTC](https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021/2 "2020-11-11T10:34:21Z")

</div>

There seems to be several problems here:

1. Kibana is unable to perform upgrade migrations because of this Elasticsearch error:  
`Unable to connect to Elasticsearch. Error: [search_phase_execution_exception] all shards failed` This could happen if you deleted any of the `.kibana*` indices while Kibana was already running which can result in a `.kibana` index instead of a `.kibana` alias. Unless you have data that you care about, the simplest would be to shutdown Kibana and then delete all the delete all the kibana indices with `DELETE .kibana*` for a blank start. Otherwise you can read more about upgrade migrations here [https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#upgrade-migrations-process](https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#upgrade-migrations-process)
2. The optimizer fails to "compile" Kibana's plugin bundles. I'm not sure why this happens, but I would suggest you start with a fresh install of Kibana to fix this problem.

---

<div class="post-metadata">

**Author:** ![hadi\_farzipour](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hadi_farzipour/32/69187_2.png) [@hadi\_farzipour](https://discuss.elastic.co/u/hadi_farzipour)\
**Post date:** [November 11, 2020, 11:31am UTC](https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021/3 "2020-11-11T11:31:54Z")

</div>

> [@rudolf](#):
>
> Unable to connect to Elasticsearch. Error

Hi  
Thanks for your comment, however i do not know how to run elasticserach queries without using kibana, I used to use Development area in order to run these commands. would you mind sending me a link in case of running commands like DELETE /.kibana\* or GET /\_cat/aliases while the kibana is unavailable  
thanks best regards

---

<div class="post-metadata">

**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\
**Post date:** [November 11, 2020, 1:49pm UTC](https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021/4 "2020-11-11T13:49:10Z")

</div>

If you prefer a GUI I would recommend using a REST client like [https://www.postman.com/product/rest-client/](https://www.postman.com/product/rest-client/) which will allow you to configure basic auth credentials and construct different request methods and bodies.

On the command line you can use curl (substitute password with your password)  
`curl -X GET "elastic:password@localhost:9200/_cat/aliases"`  
`curl -X DELETE "elastic:password@localhost:9200/.kibana*"`

---

<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 9, 2020, 1:49pm UTC](https://discuss.elastic.co/t/kibana-is-stock-on-kibana-server-is-not-ready-yet/255021/5 "2020-12-09T13:49:20Z")

</div>

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