# Clients unable to connect when gateway fails over **URL:** \ **Category:** Ignition\ **Created:** [April 29, 2016, 6:32pm UTC](https://forum.inductiveautomation.com/t/clients-unable-to-connect-when-gateway-fails-over/11604 "2016-04-29T18:32:55Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![driverk](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@driverk](https://forum.inductiveautomation.com/u/driverk)\ **Post date:** [April 29, 2016, 6:32pm UTC](https://forum.inductiveautomation.com/t/clients-unable-to-connect-when-gateway-fails-over/11604/1 "2016-04-29T18:32:55Z")
Ignition 7.8.2 Java 1.8.0\_31 We had a hung JVM today and the gateway failed over as expected. When the backup node was active, however, no clients could connect to it. We have followed the guidelines given to us by support that stated to turn off HTTP Auto-detect and to specify both gateways in the HTTP address section. The client launcher log has ERROR [SplashFrame] [11:10:43,471]: Gateway is running, but is not active. Status is: Cold ERROR [SplashFrame] [11:10:43,471]: Backup Gateway is running, but is not active. Status is: Cold But this message is inconsistent, since both the master and backup gateways show the backup gateway as active. We tested this scenario in 7.7.6 and it worked. Is there new guidance for 7.8.2 as to how redundancy should be configured?