# I get an error when connecting 2 remote clusters

**URL:** <https://discuss.elastic.co/t/i-get-an-error-when-connecting-2-remote-clusters/375029>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [February 25, 2025, 2:59pm UTC](https://discuss.elastic.co/t/i-get-an-error-when-connecting-2-remote-clusters/375029 "2025-02-25T14:59:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [February 25, 2025, 3:02pm UTC](https://discuss.elastic.co/t/i-get-an-error-when-connecting-2-remote-clusters/375029/2 "2025-02-25T15:02:01Z")

</div>

@shin12 Is this a duplicate of

> [@I get an error when connecting 2 remote clusters](https://discuss.elastic.co/t/i-get-an-error-when-connecting-2-remote-clusters/375031):
>
> However, I am encountering an issue when trying to connect Cluster 1 to Cluster 2 as a remote cluster. The nodes on both clusters are trying to communicate using their internal IP addresses (the IPs assigned to each container), but the internal IPs of the containers on the two clusters are different and cannot be on the same network, which is causing connectivity issues. I added network.host=0.0.0.0 and transport.host=0.0.0.0 to allow connections from any network interface, but the nodes still …

are you the same user as @anhle

It take a little time with the few post please be patient.

---

_[View the full topic](https://discuss.elastic.co/t/i-get-an-error-when-connecting-2-remote-clusters/375029)._
