# CrossCluster search using wrong ip address

**URL:** <https://discuss.elastic.co/t/crosscluster-search-using-wrong-ip-address/153380>\
**Category:** Elasticsearch\
**Created:** [October 22, 2018, 10:48am UTC](https://discuss.elastic.co/t/crosscluster-search-using-wrong-ip-address/153380 "2018-10-22T10:48:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manofwax](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Manofwax](https://discuss.elastic.co/u/Manofwax)\
**Post date:** [October 22, 2018, 10:48am UTC](https://discuss.elastic.co/t/crosscluster-search-using-wrong-ip-address/153380/1 "2018-10-22T10:48:34Z")

</div>

Hello, I've a local cluster A and a remote elasticsearch B deployed in a docker container.

I would like to use cluster A as a cross cluster search client to search cluster B.

I've configured cluster A in this way:  
PUT \_cluster/settings  
{  
"persistent": {  
"search": {  
"remote": {  
"cluster\_B": {  
"seeds": [  
"cluster\_B.server.local:9300"  
]  
}  
}  
}  
}  
}

But when I try to query the remote server in elasticsearch.log file on cluster A I found this error:  
`rg.elasticsearch.transport.ConnectTransportException: [SmKOedA][172.18.0.6:9300] connect_timeout[30s]`

It looks like the remote server is pushing it's internal docker ip (`172.18.0.6`) instead of the one I've configured

Is there a way to fix this behavior?

---

<div class="post-metadata">

**Author:** ![nugusbayevkk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nugusbayevkk/32/126683_2.png) [@nugusbayevkk](https://discuss.elastic.co/u/nugusbayevkk)\
**Post date:** [October 22, 2018, 11:17am UTC](https://discuss.elastic.co/t/crosscluster-search-using-wrong-ip-address/153380/2 "2018-10-22T11:17:56Z")

</div>

hi @Manofwax , what docker images are you use? version?

---

<div class="post-metadata">

**Author:** ![Manofwax](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Manofwax](https://discuss.elastic.co/u/Manofwax)\
**Post date:** [October 22, 2018, 12:28pm UTC](https://discuss.elastic.co/t/crosscluster-search-using-wrong-ip-address/153380/3 "2018-10-22T12:28:32Z")

</div>

Hello, I'm using official docker image pinned to version 6.1.4.

This is my `elasticsearch.yml` file:  
cluster.name: "ClusterB  
network.host: 0.0.0.0  
bootstrap.memory\_lock: true  
discovery.type: "single-node"  
discovery.zen.minimum\_master\_nodes: 1  
search.remote.connect: false

I think the problem is in `network.host` should I put in there the IP of the phisical machine?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 19, 2018, 12:28pm UTC](https://discuss.elastic.co/t/crosscluster-search-using-wrong-ip-address/153380/4 "2018-11-19T12:28:36Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.