# Vault health-check in a forwarding mode

**URL:** <https://discuss.hashicorp.com/t/vault-health-check-in-a-forwarding-mode/12657>\
**Category:** Vault\
**Created:** [August 11, 2020, 11:03am UTC](https://discuss.hashicorp.com/t/vault-health-check-in-a-forwarding-mode/12657 "2020-08-11T11:03:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amirsaar](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/amirsaar/32/10396_2.png) [@amirsaar](https://discuss.hashicorp.com/u/amirsaar)\
**Post date:** [August 11, 2020, 11:03am UTC](https://discuss.hashicorp.com/t/vault-health-check-in-a-forwarding-mode/12657/1 "2020-08-11T11:03:03Z")

</div>

Hi all,  
I’m configuring my vault cluster to work behind a load-balancer, as for now I’ve configured all nodes to respond to any request - active node is responding directly and standby nodes are responding to the client, by forwarding the requests internally to the active node.

I’m now at the LB configuration, if I’m using the ‘/v1/sys/health’ health check - it responses ‘429’ to each non-active node and blocks traffic to this node, so actually, even if all nodes can handle requests - only 1 nodes is considered as ‘healthy’ to the LB and all traffic is redirected to it.

How did you configure the LB on your organization?

Thanks!

---

<div class="post-metadata">

**Author:** ![amirsaar](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/amirsaar/32/10396_2.png) [@amirsaar](https://discuss.hashicorp.com/u/amirsaar)\
**Post date:** [August 13, 2020, 12:00pm UTC](https://discuss.hashicorp.com/t/vault-health-check-in-a-forwarding-mode/12657/2 "2020-08-13T12:00:26Z")

</div>

Just for the documentation - adding the parameter ‘standbyok’ solves this issue.  
For example, [http://localhost:8200/v1/sys/health?standbyok](http://localhost:8200/v1/sys/health?standbyok)