# Connecting to remote ES index from behind a proxy

**URL:** <https://discuss.elastic.co/t/connecting-to-remote-es-index-from-behind-a-proxy/195233>\
**Category:** Elasticsearch\
**Created:** [August 14, 2019, 3:49pm UTC](https://discuss.elastic.co/t/connecting-to-remote-es-index-from-behind-a-proxy/195233 "2019-08-14T15:49:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pmadley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pmadley/32/52284_2.png) [@pmadley](https://discuss.elastic.co/u/pmadley)\
**Post date:** [August 14, 2019, 3:49pm UTC](https://discuss.elastic.co/t/connecting-to-remote-es-index-from-behind-a-proxy/195233/1 "2019-08-14T15:49:23Z")

</div>

Issue: How to connect to a remote IP-restricted ES server from behind a company proxy

Background:  
We need to connect to a 3rd party IP-restricted Elasticsearch server. Our local proxy IP is whitelisted at their end, it's unlikely we can quickly get another IP whitelisted.

We cannot get our local Elasticsearch instance to connect however; it seems that environmental variables are not being picked up, so we're connecting with a non-whitelisted IP address.

It's unclear therfore how to tell Elasticsearch to use our proxy. Where should we set these values?

Many thanks.

---

<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:** [September 11, 2019, 3:49pm UTC](https://discuss.elastic.co/t/connecting-to-remote-es-index-from-behind-a-proxy/195233/2 "2019-09-11T15:49:24Z")

</div>

Closed on September 11, 2019, 3:49pm UTC

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