# Vision Client Launcher and Redundant Gateways

**URL:** <https://forum.inductiveautomation.com/t/vision-client-launcher-and-redundant-gateways/112972>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [December 23, 2025, 5:28pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-and-redundant-gateways/112972 "2025-12-23T17:28:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jay](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay](https://forum.inductiveautomation.com/u/jay)\
**Post date:** [December 23, 2025, 5:28pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-and-redundant-gateways/112972/1 "2025-12-23T17:28:26Z")

</div>

Ignition v8.1 with Vision. I have a router with port forwarding between a Vision client (192.168.40.21) and redundant Ignition gateways (192.168.30.11 and 192.168.30.12). The router address is 192.168.40.1. Router port 8088 is forwarded to the primary gateway (192.168.30.11) port 8088. Port 8089 is forwarded to the backup gateway (192.168.30.12) port 8088. How do i setup up the Client Launcher to automatically switch to the backup gateway when the primary fails?

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [December 23, 2025, 5:48pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-and-redundant-gateways/112972/2 "2025-12-23T17:48:41Z")

</div>

Don't believe that is going to work. The vision launcher gets the redundancy info when it connects the first time to the master. But the master has no idea about anything to do with your network setup. So it's going to just tell the client it would need to fallback to the 192.168.30.12 address.

You need to change your router configuration so it allows comms between the 192.168.40.x network and the 192.168.30.x network (or at least, those IPs that need to talk)

---

<div class="post-metadata">

**Author:** ![jay](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay](https://forum.inductiveautomation.com/u/jay)\
**Post date:** [December 23, 2025, 7:13pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-and-redundant-gateways/112972/3 "2025-12-23T19:13:11Z")

</div>

Hmm… This means that a Vision client cannot be launched after a gateway failover. This seems to be an oversight in the version 8 Client Launcher design. In version 7.9 the backup gateway could be specified as an argument to the launcher.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [December 23, 2025, 7:21pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-and-redundant-gateways/112972/4 "2025-12-23T19:21:37Z")

</div>

In your user folder under the `.ignition\clientlauncher-data\vision-client-launcher.json` file, there should be a section for your project that says `redundant.gateways` and by default without redundancy it will be a blank list/array `[]` but you can add/edit your gateway there to be `["http://192.168.40.1:8089"]` and see if it keeps that or overrides it when you launch it.

You could also try setting your Gateway settings for Networking --\> Web Server --\> Public HTTP Address to use your 192.168.40.1 IP and 8088 for the primary and 8089 for the backup to see if that fixes your issue.

You're using NAT and you should really be using routing instead with the firewall allowing the client to access the redundant servers directly instead of through port forwarding.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/5/9577e56619d761246574a0f4d466f1260323e087.png)