# Ignition Failover

**URL:** <https://forum.inductiveautomation.com/t/ignition-failover/116240>\
**Category:** General Discussion\
**Created:** [July 1, 2026, 9:21pm UTC](https://forum.inductiveautomation.com/t/ignition-failover/116240 "2026-07-01T21:21:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jay\_collosi](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@jay\_collosi](https://forum.inductiveautomation.com/u/jay_collosi)\
**Post date:** [July 1, 2026, 9:21pm UTC](https://forum.inductiveautomation.com/t/ignition-failover/116240/1 "2026-07-01T21:21:13Z")

</div>

Do you know if Ignition supports Windows Server Failover Clustering (WSFC)?

We have Ignition (8.1.53) configured in a Master/Backup on two different servers. Both are licensed for redundancy.

An external application is calling Primary at name [ignition1.xxx.com](http://ignition1.xxx.com), when primary fails, ignition fails over to backup. But the external application doesn't change over to [ignition2.xxx.com](http://ignition2.xxx.com) address.

Does anybody have any ideas on how to accomplish this? Please let me know.

thank you in advance

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 1, 2026, 10:00pm UTC](https://forum.inductiveautomation.com/t/ignition-failover/116240/2 "2026-07-01T22:00:46Z")

</div>

Ignition has no special code for WSFC, whatever that actually means in practice.  
If that feature can act like a reverse proxy/load balancer, then the answer I just gave in this other thread basically applies:

> [@Web Development Module and Redundancy](https://forum.inductiveautomation.com/t/web-development-module-and-redundancy/116238/2):
>
> A load balancer/reverse proxy is the generally accepted solution to this, but be aware they have no concept of Ignition's specific redundancy concept. You'll have to use a product smart enough to distinguish between HTTP availability (whether the given redundant node is up at all) and Ignition's specific redundancy role (i.e. don't try to fail requests over to a backup that is not active). You can do this by checking the /system/gwinfo route.