# Kibana server is not ready yet issue after upgrade to 6.5.0

**URL:** <https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021>\
**Category:** Kibana\
**Created:** [November 16, 2018, 10:13am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021 "2018-11-16T10:13:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Guillain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guillain/32/23301_2.png) [@Guillain](https://discuss.elastic.co/u/Guillain)\
**Post date:** [November 20, 2018, 3:04pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/4 "2018-11-20T15:04:43Z")

</div>

Thanks,

FYI with this kind of logs and on my side it was an index issue on .kibana.  
Simple way to fix it is to adapt the kibana's index in the `kibana.yml` file (and back to the original value after have getting back the hand on the GUI.  
Ie:  
`kibana.index: ".newkibana"`

---

_[View the full topic](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021)._