# Kibana server is not ready yet

**URL:** <https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [September 7, 2022, 7:19pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925 "2022-09-07T19:19:55Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Boodle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boodle/32/86046_2.png) [@Boodle](https://discuss.elastic.co/u/Boodle)\
**Post date:** [September 7, 2022, 7:19pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/1 "2022-09-07T19:19:56Z")

</div>

Have a 3 node cluster for elasticsearch on docker  
server1(recently upgraded to 7.17.6),  
server2(On 7.10.1),  
server3(On 7.10.1) and a single Kibana(recently upgraded to 7.17.6) instance on server1. All 3 ES nodes & kibana containers comes up fine.

Error:  
Kibana container started fine but frontend throws error "Kibana server is not ready yet".

Troubleshooting steps performed **but no luck** :  
Resolution 1) `sudo curl -k -XDELETE https://<Host-Name>:<Kib-PortNo>/*kibana* -u username:password`  
Output: Kibana server is not ready yet -- On terminal

Resolution 2) Checked Kibana.yml & elasticsearch.yml. Changed to below settings as suggested in a forum.

```auto
elasticsearch.yml
network.host: 0.0.0.0

```

changed kibana.yml From

```auto
server.name: kibana
server.host: "0"
elasticsearch.hosts: ["http://elasticsearch:9200"]
monitoring.ui.container.elasticsearch.enabled: true

```

To

```auto
server.name: kibana
server.host: "0"
#elasticsearch.hosts: ["http://elasticsearch:9200"]
elasticsearch.hosts: 0.0.0.0
monitoring.ui.container.elasticsearch.enabled: true

```

1. sudo curl -u username:password https:// \<Host\_Name\>:\<elastic\_PortNo\> -k gives the outcome

```auto
 "name" : "<name>",
  "cluster_name" : "<cluster-name>",
  "cluster_uuid" : "<uuid-number>",
  "version" : {
    "number" : "7.17.6",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : " ",
    "build_date" : "",
    "build_snapshot" : false,
    "lucene_version" : "8.11.1",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },

```

below docker-compose.yml file for kibana.

```auto
version: '2.2'

services:
  kib11:
    image: docker.elastic.co/kibana/kibana:${VERSION}
    container_name: kib11
    ports:
      - 5602:5601
    environment:
      SERVERNAME: localhost
      ELASTICSEARCH_URL: https://<>: 9200
      ELASTICSEARCH_HOSTS: https://<>: 9200
      ELASTICSEARCH_USERNAME: <>
      ELASTICSEARCH_PASSWORD: <>
      ELASTICSEARCH_SSL_CERTIFICATE_AUTHORITIES: <>
      ELASTICSEARCH_SSL_VERIFICATIONMODE: none
      SERVER_SSL_ENABLED: "true"
      SERVER_SSL_KEYSTORE_PATH: <>
    volumes:
      - kib-config:/usr/share/kibana/config
      - kib-data:/usr/share/kibana/data
      - kib-log:/usr/share/kibana/logs
    networks:
      - elastic

```

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [September 7, 2022, 8:54pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/2 "2022-09-07T20:54:21Z")

</div>

Check /usr/share/kibana/logs

---

<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:** [September 7, 2022, 9:10pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/3 "2022-09-07T21:10:58Z")

</div>

Why are you running mixed versions like this?

---

<div class="post-metadata">

**Author:** ![Boodle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boodle/32/86046_2.png) [@Boodle](https://discuss.elastic.co/u/Boodle)\
**Post date:** [September 7, 2022, 9:14pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/4 "2022-09-07T21:14:49Z")

</div>

don't see kibana folder under /usr/share/. There is another at location \<....\>/kib11/log/ but no file in it.

---

<div class="post-metadata">

**Author:** ![Boodle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boodle/32/86046_2.png) [@Boodle](https://discuss.elastic.co/u/Boodle)\
**Post date:** [September 7, 2022, 9:18pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/5 "2022-09-07T21:18:04Z")

</div>

I get another error while trying to upgrade server2 so I'm stuck in the middle of upgrade.  
Server1 upgrade went fine without any other error except this on kibana.

---

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [September 8, 2022, 12:20pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/6 "2022-09-08T12:20:53Z")

</div>

> [@Boodle](#):
>
> I get another error while trying to upgrade server2

I think we should start with solving this issue. Could you please paste it here?

---

<div class="post-metadata">

**Author:** ![tom.verbeek](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tom.verbeek](https://discuss.elastic.co/u/tom.verbeek)\
**Post date:** [September 8, 2022, 12:34pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/7 "2022-09-08T12:34:12Z")

</div>

you can check in your Kibana.yml where your logs are being saved. it could be /kibana/logs

---

<div class="post-metadata">

**Author:** ![Boodle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boodle/32/86046_2.png) [@Boodle](https://discuss.elastic.co/u/Boodle)\
**Post date:** [September 9, 2022, 7:05pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/8 "2022-09-09T19:05:46Z")

</div>

don't see the location as mentioned. someone asked to check the logs in /var/log/messages. not sure if it captures.  
P.S. The issue in description is resolved but still would be interested if it's the right location. Thanks

---

<div class="post-metadata">

**Author:** ![Boodle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boodle/32/86046_2.png) [@Boodle](https://discuss.elastic.co/u/Boodle)\
**Post date:** [September 9, 2022, 7:07pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/9 "2022-09-09T19:07:59Z")

</div>

Thanks, Resolved the issue on server2 and upgraded all nodes fine to 7.17.6. Later 'Kibana server is not ready yet' got resolved as well. so may be Kibana lookes for all nodes to be on the same upgraded version for it to be up.Thanks

---

<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:** [October 7, 2022, 7:08pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/313925/10 "2022-10-07T19:08:11Z")

</div>

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