# Kibana server is not ready yet issue after upgrade to 6.5.0 **URL:** \ **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:** 9\ **Page:** 1
**Author:** ![nuwan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nuwan/32/42325_2.png) [@nuwan](https://discuss.elastic.co/u/nuwan)\ **Post date:** [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/1 "2018-11-16T10:13:13Z")
Since last night I experience the error message "Kibana server is not ready yet" in the browser when I want to open Kibana. I have upgrade kibana and Elasticsearch to V 6.5.0 . I've done a lot of research, but I can't find the reason. [root@915452-IngestionDemo ~]# curl [http://172.24.36.216:9200](http://172.24.36.216:9200) { "name" : "[915452-IngestionDemo.newfrontierdata.com](http://915452-IngestionDemo.newfrontierdata.com)", "cluster\_name" : "IngestionDemO", "cluster\_uuid" : "9S5ICK\_ITiOMhpdz6sGEgQ", "version" : { "number" : "6.5.0", "build\_flavor" : "default", "build\_type" : "rpm", "build\_hash" : "816e6f6", "build\_date" : "2018-11-09T18:58:36.352602Z", "build\_snapshot" : false, "lucene\_version" : "7.5.0", "minimum\_wire\_compatibility\_version" : "5.6.0", "minimum\_index\_compatibility\_version" : "5.0.0" }, "tagline" : "You Know, for Search" } {"type":"log","@timestamp":"2018-11-16T09:54:34Z","tags":["warning","stats-collection"],"pid":9031,"message":"Unable to fetch data from canvas collector"} {"type":"error","@timestamp":"2018-11-16T09:54:34Z","tags":["warning","stats-collection"],"pid":9031,"level":"error","error":{"message":"[search\_phase\_execution\_exception] all shards failed","name":"Error","stack":"[search\_phase\_execution\_exception] all shards failed :: {"path":"/.kibana/\_search","query":{"ignore\_unavailable":true,"filter\_path":"aggregations.types.buckets"},"body":"{\"size\":0,\"query\":{\"terms\":{\"type\":[\"dashboard\",\"visualization\",\"search\",\"index-pattern\",\"graph-workspace\",\"timelion-sheet\"]}},\"aggs\":{\"types\":{\"terms\":{\"field\":\"type\",\"size\":6}}}}","statusCode":503,"response":"{\"error\":{\"root\_cause\":,\"type\":\"search\_phase\_execution\_exception\",\"reason\":\"all shards failed\",\"phase\":\"query\",\"grouped\":true,\"failed\_shards\":},\"status\":503}"}\n at respond (/usr/share/kibana/node\_modules/elasticsearch/src/lib/transport.js:308:15)\n at checkRespForFailure (/usr/share/kibana/node\_modules/elasticsearch/src/lib/transport.js:267:7)\n at HttpConnector. (/usr/share/kibana/node\_modules/elasticsearch/src/lib/connectors/http.js:165:7)\n at IncomingMessage.wrapper (/usr/share/kibana/node\_modules/elasticsearch/node\_modules/lodash/lodash.js:4949:19)\n at emitNone (events.js:111:20)\n at IncomingMessage.emit (events.js:208:7)\n at endReadableNT (\_stream\_readable.js:1064:12)\n at \_combinedTickCallback (internal/process/next\_tick.js:138:11)\n at process.\_tickCallback (internal/process/next\_tick.js:180:9)"},"message":"[search\_phase\_execution\_exception] all shards failed"} {"type":"log","@timestamp":"2018-11-16T09:54:34Z","tags":["warning","stats-collection"],"pid":9031,"message":"Unable to fetch data from kibana collector"} ---
**Author:** ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)\ **Post date:** [November 16, 2018, 10:26am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/2 "2018-11-16T10:26:19Z")
@Nuwan, 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? One more reason can be have you upgraded your all elasticsearch node on version 6.5.0 as well as kibana also on 6.5.0? If any one of them are still on the older version then there might be compatibility issue. So please check it also. Thanks. ---
**Author:** ![nuwan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nuwan/32/42325_2.png) [@nuwan](https://discuss.elastic.co/u/nuwan)\ **Post date:** [November 16, 2018, 2:42pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/3 "2018-11-16T14:42:45Z")
Hi Thank you very much . your guidance and following link helped to solve that issue [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). ---
**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")
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"` ---
**Author:** ![nuwan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nuwan/32/42325_2.png) [@nuwan](https://discuss.elastic.co/u/nuwan)\ **Post date:** [November 27, 2018, 10:07am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/5 "2018-11-27T10:07:45Z")
Thank you .Issue was fix after removing kibana related index and restart the kibana service ---
**Author:** ![jaleel27](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaleel27/32/38474_2.png) [@jaleel27](https://discuss.elastic.co/u/jaleel27)\ **Post date:** [December 5, 2018, 1:34pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/6 "2018-12-05T13:34:30Z")
check for elasticsearch version, if it is not same version as kibana. please update. I had the same issue, I have upgraded the elasticsearch to 6.5. then after restarting the services. the issue sorted out. Good Day.. ---
**Author:** ![nuwan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nuwan/32/42325_2.png) [@nuwan](https://discuss.elastic.co/u/nuwan)\ **Post date:** [December 10, 2018, 5:18am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/7 "2018-12-10T05:18:56Z")
Thank you very much. This issue is fixed now ---
**Author:** ![Naresh\_Yadav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/naresh_yadav/32/39064_2.png) [@Naresh\_Yadav](https://discuss.elastic.co/u/Naresh_Yadav)\ **Post date:** [December 20, 2018, 6:22pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/8 "2018-12-20T18:22:29Z")
Thanks @Guillain it resolves my issue which i am struggling for very long time ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 17, 2019, 6:22pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/9 "2019-01-17T18:22:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.