# How to resolve Unable to revive connection and No living connections
**URL:** https://discuss.elastic.co/t/how-to-resolve-unable-to-revive-connection-and-no-living-connections/247836
**Category:** Kibana
**Tags:** docker
**Created:** [September 8, 2020, 7:52am UTC](https://discuss.elastic.co/t/how-to-resolve-unable-to-revive-connection-and-no-living-connections/247836 "2020-09-08T07:52:17Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@CHAIRUL\_ANWAR](https://discuss.elastic.co/u/CHAIRUL_ANWAR)
#### Post date: [September 8, 2020, 7:52am UTC](https://discuss.elastic.co/t/how-to-resolve-unable-to-revive-connection-and-no-living-connections/247836/1 "2020-09-08T07:52:17Z")
i create docker container on my environment
> 1. docker run -d --name elasticsearch --restart always -p 9200:9200 -p 9300:9300 -e "ES\_JAVA\_OPTS=-Xms1024m -Xmx1024m" -e "discovery.type=single-node" elasticsearch:7.4.0
> 1. docker run -d --name logstash --restart always -p 5555:5555/udp -p 5044:5044 -p 9600:9600 -e "ELASTICSEARCH\_URL=[http://elasticsearch:9200](http://elasticsearch:9200)" -v /home/ubuntu/logstash/pipeline:/usr/share/logstash/pipeline/ logstash:7.4.0
> 1. docker run -d --name kibana --restart always -p 5601:5601 -e "ELASTICSEARCH\_URL=[http://elasticsearch:9200](http://elasticsearch:9200)" kibana:7.4.0
but the kibana web say "Kibana server is not ready yet"
i check on kibana logs
it say
> {"type":"log","@timestamp":"2020-09-08T07:05:59Z","tags":["license","warning","xpack"],"pid":7,"message":"License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Error: No Living connections"}
> {"type":"log","@timestamp":"2020-09-08T07:06:00Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"Unable to revive connection: [http://elasticsearch:9200/](http://elasticsearch:9200/)"}
> {"type":"log","@timestamp":"2020-09-08T07:06:00Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"No living connections"}
> {"type":"log","@timestamp":"2020-09-08T07:06:02Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"Unable to revive connection: [http://elasticsearch:9200/](http://elasticsearch:9200/)"}
> {"type":"log","@timestamp":"2020-09-08T07:06:02Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"No living connections"}
> {"type":"log","@timestamp":"2020-09-08T07:06:05Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"Unable to revive connection: [http://elasticsearch:9200/](http://elasticsearch:9200/)"}
> {"type":"log","@timestamp":"2020-09-08T07:06:05Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"No living connections"}
> {"type":"log","@timestamp":"2020-09-08T07:06:07Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"Unable to revive connection: [http://elasticsearch:9200/](http://elasticsearch:9200/)"}
> {"type":"log","@timestamp":"2020-09-08T07:06:07Z","tags":["warning","elasticsearch","admin"],"pid":7,"message":"No living connections"}
plis i need help thx
---
### Author:  [@flash1293](https://discuss.elastic.co/u/flash1293)
#### Post date: [September 9, 2020, 12:13pm UTC](https://discuss.elastic.co/t/how-to-resolve-unable-to-revive-connection-and-no-living-connections/247836/2 "2020-09-09T12:13:36Z")
It looks like you are not linking your docker containers. By default they are running in the "bridge" network mode - this doesn't include resolving other containers by name: [Docker run reference | Docker Docs](https://docs.docker.com/engine/reference/run/#network-settings)
> NETWORK: BRIDGE
> Containers can communicate via their IP addresses by default. To communicate by name, they must be linked.
Because of this, the Kibana instance running in the Kibana container can't find the Elasticsearch container by `elasticsearch` host name.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 7, 2020, 12:13pm UTC](https://discuss.elastic.co/t/how-to-resolve-unable-to-revive-connection-and-no-living-connections/247836/3 "2020-10-07T12:13:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.