# Web Development Module and Redundancy

**URL:** <https://forum.inductiveautomation.com/t/web-development-module-and-redundancy/116238>\
**Category:** Ignition\
**Created:** [July 1, 2026, 7:46pm UTC](https://forum.inductiveautomation.com/t/web-development-module-and-redundancy/116238 "2026-07-01T19:46:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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, 9:59pm UTC](https://forum.inductiveautomation.com/t/web-development-module-and-redundancy/116238/2 "2026-07-01T21:59:51Z")

</div>

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.

---

_[View the full topic](https://forum.inductiveautomation.com/t/web-development-module-and-redundancy/116238)._