# Getting "Kibana server is not ready yet" when running from docker **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [May 22, 2022, 7:27am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345 "2022-05-22T07:27:07Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![asil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asil/32/97607_2.png) [@asil](https://discuss.elastic.co/u/asil)\ **Post date:** [May 22, 2022, 7:27am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/1 "2022-05-22T07:27:07Z")
I'm trying to run `elasticsearch` and `kibana` via dockers, and I'm getting errors with `kibana` . I'm using `elasticsearch` and `kibana` version 7.6.2 and `Ubuntu 18.04.6 LTS` I run `elasticsearch` with the following command: ```auto docker run -p 127.0.0.1:9200:9200 -p 127.0.0.1:9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:7.6.2 ``` And it seems that `elasticsearch` is on (I can bulk documents and get information about the index from `python` code). I'm running `kibana` with the following commands: ```auto docker network create elastic docker run --net elastic -p 127.0.0.1:5601:5601 -e "ELASTICSEARCH_HOSTS=http://127.0.0.1:9200" docker.elastic.co/kibana/kibana:7.6.2 ``` I see the following message in the web browser: `Kibana server is not ready yet` And I see the following logs in the console: ```auto {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["info","savedobjects-service"],"pid":7,"message":"Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations..."} {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["error","elasticsearch","data"],"pid":7,"message":"Request error, retrying\nHEAD http://127.0.0.1:9200/.apm-agent-configuration => connect ECONNREFUSED 127.0.0.1:9200"} {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["error","elasticsearch","data"],"pid":7,"message":"Request error, retrying\nGET http://127.0.0.1:9200/_xpack => connect ECONNREFUSED 127.0.0.1:9200"} {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["error","elasticsearch","admin"],"pid":7,"message":"Request error, retrying\nGET http://127.0.0.1:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip => connect ECONNREFUSED 127.0.0.1:9200"} {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"Unable to revive connection: http://127.0.0.1:9200/"} {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"No living connections"} Could not create APM Agent configuration: No Living connections {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"Unable to revive connection: http://127.0.0.1:9200/"} {"type":"log","@timestamp":"2022-05-22T06:45:20Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"No living connections"} ``` How can I run kibana via docker ? ---
**Author:** ![ibra\_013](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibra_013/32/104827_2.png) [@ibra\_013](https://discuss.elastic.co/u/ibra_013)\ **Post date:** [May 22, 2022, 8:15am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/2 "2022-05-22T08:15:19Z")
Hi @asil can you add this environment `server.host=0` when running kibana docker . ---
**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:** [May 22, 2022, 9:50pm UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/3 "2022-05-22T21:50:49Z")
> [@asil](#): > > `connect ECONNREFUSED 127.0.0.1:9200"}` Is Elasticsearch available, up and running? Check by curl, if is possible. ---
**Author:** ![asil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asil/32/97607_2.png) [@asil](https://discuss.elastic.co/u/asil)\ **Post date:** [May 23, 2022, 8:57am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/4 "2022-05-23T08:57:32Z")
Same results. I run kibana with: docker run --net elastic -p 127.0.0.1:5601:5601 -e "server.host=0" -e "ELASTICSEARCH\_HOSTS=[http://127.0.0.1:9200](http://127.0.0.1:9200)" [docker.elastic.co/kibana/kibana:7.6.2](http://docker.elastic.co/kibana/kibana:7.6.2) And got same results: > "type":"log","@timestamp":"2022-05-23T08:48:21Z","tags":["warning","plugins","licensing"],"pid":8,"message":"License information could not be obtained from Elasticsearch due to Error: No Living connections error"} > {"type":"log","@timestamp":"2022-05-23T08:48:21Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"Unable to revive connection: [http://127.0.0.1:9200/](http://127.0.0.1:9200/)"} ---
**Author:** ![ibra\_013](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibra_013/32/104827_2.png) [@ibra\_013](https://discuss.elastic.co/u/ibra_013)\ **Post date:** [May 23, 2022, 10:06am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/5 "2022-05-23T10:06:48Z")
Hi @asil as @Rios mentioned, ES is running? ```auto curl -XGET http://localhost:9200 ``` ---
**Author:** ![asil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asil/32/97607_2.png) [@asil](https://discuss.elastic.co/u/asil)\ **Post date:** [May 23, 2022, 10:57am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/6 "2022-05-23T10:57:15Z")
Elastic is running (I can work with it via python code) ---
**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:** [May 23, 2022, 11:07am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/7 "2022-05-23T11:07:22Z")
> [@asil](#): > > :"License information could not be obtained from Elasticsearch due to Error: No Living connections error"} I had similar issues. Kibana cannot see own system indices or they were corrupted, and ES what up. Have you tried to restart ES? Is it possible? ---
**Author:** ![asil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asil/32/97607_2.png) [@asil](https://discuss.elastic.co/u/asil)\ **Post date:** [May 23, 2022, 11:59am UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/8 "2022-05-23T11:59:21Z")
I have tried to restart ES - \> got same error message ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [May 23, 2022, 12:08pm UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/9 "2022-05-23T12:08:17Z")
> [@asil](#): > > "ELASTICSEARCH\_HOSTS=[http://127.0.0.1:9200](http://127.0.0.1:9200)" Is elasticsearch running in the same docker container as Kibana? This configuration will make Kibana try to connect to an elasticsearch instance running in the same container, it won't work if elasticsearch is running in a different container. You should use docker-compose, check the [documentation](https://www.elastic.co/guide/en/elastic-stack-get-started/7.17/get-started-docker.html) for version 7.X. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 20, 2022, 12:08pm UTC](https://discuss.elastic.co/t/getting-kibana-server-is-not-ready-yet-when-running-from-docker/305345/10 "2022-06-20T12:08:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.