# Configure NGINX Proxy for Elastic

**URL:** <https://discuss.elastic.co/t/configure-nginx-proxy-for-elastic/337462>\
**Category:** Elasticsearch\
**Created:** [July 3, 2023, 1:30pm UTC](https://discuss.elastic.co/t/configure-nginx-proxy-for-elastic/337462 "2023-07-03T13:30:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TomTom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomtom/32/3676_2.png) [@TomTom](https://discuss.elastic.co/u/TomTom)\
**Post date:** [July 3, 2023, 1:30pm UTC](https://discuss.elastic.co/t/configure-nginx-proxy-for-elastic/337462/1 "2023-07-03T13:30:52Z")

</div>

I configured three nodes as master.

I created a certificate for each one, which is used in HTTP and Transport requests.

There is also a username with a password to access the elasticsearch.

Note: Since I created the certificate, I need to pass the `-k` parameter when performing a cURL.

My Elasticsearch is only listening for the local machine IP.

However, who will access this VM will be other VMs also using the local IP of the nginx proxy and also remotely for some selected IPs, using the public IP of nginx.

My question is how do I configure an nginx proxy to connect to these three machines, requiring the username and password to still perform requests via HTTPs?

---

<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:** [July 31, 2023, 1:31pm UTC](https://discuss.elastic.co/t/configure-nginx-proxy-for-elastic/337462/2 "2023-07-31T13:31:14Z")

</div>

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