# Elasticsearch cluster across multiple docker hosts

**URL:** https://discuss.elastic.co/t/elasticsearch-cluster-across-multiple-docker-hosts/358314
**Category:** Elasticsearch
**Tags:** docker
**Created:** [April 26, 2024, 7:30pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-across-multiple-docker-hosts/358314 "2024-04-26T19:30:08Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [April 26, 2024, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-across-multiple-docker-hosts/358314/2 "2024-04-26T20:41:04Z")

</div>

Hi Janusz and welcome!

I'd suggest looking at [these docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html), particularly the section on [binding and publishing](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#modules-network-binding-publishing) to understand better how Elasticsearch needs its network to be configured. Basically it looks like your nodes are not accessible at their transport publish addresses. It can be tricky to get everything lined up correctly in Docker since it all depends on exactly how your environment is configured.

In particular the `followup connection failed` message indicates that node `es01` is accessible at `172.18.0.1:19300`, but it thinks its address is `172.23.0.3:9300` and it is not accessible at this address. You either need to make it accessible at that address, or else adjust its publish address to one at which it is accessible.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-cluster-across-multiple-docker-hosts/358314)._