# Kibana Error Connecting to ES on Docker - Cannot Revive Connection

**URL:** https://discuss.elastic.co/t/kibana-error-connecting-to-es-on-docker-cannot-revive-connection/133335
**Category:** Kibana
**Created:** [May 25, 2018, 2:58pm UTC](https://discuss.elastic.co/t/kibana-error-connecting-to-es-on-docker-cannot-revive-connection/133335 "2018-05-25T14:58:15Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jen-huang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jen-huang/32/74327_2.png) [@jen-huang](https://discuss.elastic.co/u/jen-huang)
#### Post date: [May 25, 2018, 4:40pm UTC](https://discuss.elastic.co/t/kibana-error-connecting-to-es-on-docker-cannot-revive-connection/133335/2 "2018-05-25T16:40:42Z")

</div>

Your Elasticsearch container name is `elasticsearch-products-624`. Kibana's Elasticsearch URL should match - change to `http://elasticsearch-products-624:9200`.

More info:

> [@Kibana docker image doesn't connect to elasticsearch image](https://discuss.elastic.co/t/kibana-docker-image-doesnt-connect-to-elasticsearch-image/79511/4):
>
> Hi. This one is all about [Docker Networking](https://docs.docker.com/engine/userguide/networking/). There are some steps involved in getting Docker to establish network links and name resolution between containers. It's one of the reasons I tend to recommend getting started with Docker Compose, since it takes care of some of these details. The Kibana image tries, by default, to connect to a host/container called elasticsearch. However, the Docker operator must arrange for that name to make sense, and for there to be a network connection between th…

---

_[View the full topic](https://discuss.elastic.co/t/kibana-error-connecting-to-es-on-docker-cannot-revive-connection/133335)._