Ignition 8.3.9 – Vision Client fails to switch to Backup Gateway despite successful redundancy failover

Ignition
1

Ignition 8.3.9 – Vision Client not switching to Backup Gateway

Hello,

We are experiencing an issue with Vision Client failover in an Ignition redundant architecture.

System Configuration

  • Ignition Version: 8.3.9 (b2026082511)
  • Operating System: Windows 11 64-bit (both PCs)
  • Master Gateway: 192.168.54.5:8088
  • Backup Gateway: 192.168.54.6:8088
  • Redundancy: Port 8060, SSL enabled
  • Vision Clients: Running on both PCs, connected to the Master Gateway.

Problem Description

Gateway redundancy appears to work correctly.

Both Gateways show:

  • Peer Connected: Yes
  • Synchronization Status: Good
  • Master Activity Level: Active
  • Backup Activity Level: Warm

When we stop the Ignition service on the Master PC, the Backup Gateway correctly transitions from Warm to Active.

However, the Vision Client running on the secondary PC does not automatically switch to the Backup Gateway and remains disconnected.

During normal operation however Vision Diagnostics already shows something is not working accordingly:

MASTER diagnostic connection tab:
   Connected to Master http://0.0.0.0:8088
   Backup connection status is unknown

When the Master Ignition service is stopped:

Screenshot 2026-10-19 alle 10.40.29
Screenshot 2026-10-19 alle 10.40.291920×1094 389 KB

Gateway Connection Lost

Master is not available
java.net.ConnectException: Connection refused

Backup connection status is unknown.
Searching for active Gateway

We also noticed that the Vision Client running on the primary PC displays http://0.0.0.0:8088 as the Master address in Diagnostics, while the secondary PC correctly displays 192.168.54.5:8088.

Troubleshooting Performed

We have already tried the following:

  • Verified Gateway redundancy configuration and synchronization.
  • Confirmed that the Backup Gateway correctly becomes Active when the Master stops.
  • Performed redundancy resynchronization successfully.
  • Deleted the Ignition/Vision Client cache on Windows 11.
  • Downloaded and reinstalled the Vision Client Launcher.
  • Reconfigured and restarted the Vision Client, pointing it to the correct Master IP address.

Despite these attempts, the issue persists, and we have not been able to identify the root cause.

Questions

  1. Is there any additional configuration required in Ignition 8.3.9 for automatic Vision Client failover?
  2. Why does Vision report "Backup connection status is unknown" even though Gateway redundancy is working correctly?
  3. Could this be related to the Gateway HTTP address configuration or Vision Client Launcher settings?
  4. Is this a known issue or regression in Ignition 8.3.9?

The Gateway redundancy mechanism seems to be working correctly, but the Vision Clients do not appear to recognize the Backup Gateway.

Any suggestions or troubleshooting recommendations would be greatly appreciated.

Thank you!

2

What do you gateways report as their public HTTP(S) address? Do the gateways talk to each other over the same IP addresses that clients use? (The latter is generally required to use "automatic" in your gateway public address setting.)

For best results, use DNS names everywhere in your settings, set each gateway to use its DNS name as its public address (not automatic), and ensure the DNS names resolve correctly everywhere you run clients.

3

Hi, thanks for your reply.

I’ve done some additional testing using Auto Detect HTTP Address.

The Master Gateway now correctly reports its IP address, but the Backup Gateway still shows “Connection Status: Unknown” in the Vision Client diagnostics.

image
image1098×962 143 KB

My current configuration is:

  • Master Gateway: 192.168.54.5
  • Backup Gateway: 192.168.54.6

Both gateways are on the same local network.

I can also reproduce the issue by manually triggering a Request Failover from the backup server.

When I do this:

  • The Backup Gateway correctly becomes active.
  • The redundancy failover appears to work correctly at the Gateway level.
  • However, the Vision Client does not reconnect to the Backup Gateway and remains in an error state, apparently because it doesn’t know the backup server’s address.

In the Vision Client diagnostics, I currently see:

Master: Connected to http://192.168.54.5:8088
Backup: Connection status is unknown.

Both Gateway IP addresses are reachable from the client network.

I understand that using DNS names instead of IP addresses is recommended, but since both gateways and clients are on the same local network, I would first like to understand why the backup address is not being detected correctly.

Is there a specific setting in Ignition 8.3 where I need to configure the Backup Gateway’s public HTTP address so that Vision Clients can discover it correctly?

Thanks for your help!