# Elastic search behind nginx proxy - Node updates

**URL:** <https://discuss.elastic.co/t/elastic-search-behind-nginx-proxy-node-updates/368968>\
**Category:** Elasticsearch\
**Created:** [October 17, 2024, 5:26am UTC](https://discuss.elastic.co/t/elastic-search-behind-nginx-proxy-node-updates/368968 "2024-10-17T05:26:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deeraj\_Theepshi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deeraj_theepshi/32/138442_2.png) [@Deeraj\_Theepshi](https://discuss.elastic.co/u/Deeraj_Theepshi)\
**Post date:** [October 17, 2024, 5:26am UTC](https://discuss.elastic.co/t/elastic-search-behind-nginx-proxy-node-updates/368968/1 "2024-10-17T05:26:12Z")

</div>

I have a setup such that I'm proxying requests over a custom domain that points to an nginx server to Elasticsearch cluster.

I have noticed that nginx is caching the data node ips as per the ttl. Now, when a node goes down or when blue green deployments happen, until the ttl is expired nginx is routing the requests to nodes that aren't active anymore.

Has anyone else faced this issue ? How do we solve this ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 17, 2024, 8:46am UTC](https://discuss.elastic.co/t/elastic-search-behind-nginx-proxy-node-updates/368968/2 "2024-10-17T08:46:17Z")

</div>

I think this is more a question of your Nginx config than anything particularly to do with Elasticsearch. See in particular its documentation on [HTTP health checks](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-health-check/) and [TCP health checks](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-health-check/). If you need more help, I'd recommend finding a forum dedicated to Nginx questions rather than this Elasticsearch-focussed one.