# Elasticsearch Cross Cluster Search behind nginx proxy

**URL:** <https://discuss.elastic.co/t/elasticsearch-cross-cluster-search-behind-nginx-proxy/142706>\
**Category:** Elasticsearch\
**Created:** [August 2, 2018, 7:52am UTC](https://discuss.elastic.co/t/elasticsearch-cross-cluster-search-behind-nginx-proxy/142706 "2018-08-02T07:52:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kalash969](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kalash969/32/34001_2.png) [@kalash969](https://discuss.elastic.co/u/kalash969)\
**Post date:** [August 2, 2018, 7:52am UTC](https://discuss.elastic.co/t/elasticsearch-cross-cluster-search-behind-nginx-proxy/142706/1 "2018-08-02T07:52:06Z")

</div>

I want to setup sort of aggregation for multiple Elasticsearch clusters based on Cross Cluster Search feature. I have the following layout:

![Untitled%20Diagram](https://us1.discourse-cdn.com/elastic/original/3X/8/d/8dbc4c3fa81675a504f91332eb3535ea4cfe94ef.png)

As seed for Cross Cluster Search I am using the only available via network cluster address. After querying I am getting error:

```
[elasticsearch][172.16.10.100:9300] connect_timeout[30s]

```

I can't change `publish_host` for nodes, because that address used inside the cluster for node communication.

Is there any option to force Cross Cluster Search to use only provided address? Or any other way to setup kinda proxy for user to be able to search/visualize in kibana data from multiple isolated elasticsearch clusters?

---

<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:** [August 30, 2018, 7:52am UTC](https://discuss.elastic.co/t/elasticsearch-cross-cluster-search-behind-nginx-proxy/142706/2 "2018-08-30T07:52:09Z")

</div>

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