# Redundancy not working with docker standard example

**URL:** <https://forum.inductiveautomation.com/t/redundancy-not-working-with-docker-standard-example/103993>\
**Category:** Ignition\
**Created:** [March 21, 2025, 4:18am UTC](https://forum.inductiveautomation.com/t/redundancy-not-working-with-docker-standard-example/103993 "2025-03-21T04:18:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohamad.tayara](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mohamad.tayara](https://forum.inductiveautomation.com/u/mohamad.tayara)\
**Post date:** [March 21, 2025, 4:18am UTC](https://forum.inductiveautomation.com/t/redundancy-not-working-with-docker-standard-example/103993/1 "2025-03-21T04:18:56Z")

</div>

I am getting duplicate connection on the backup gw ( gateway network outgoing connection)! redundancy on port 8088 no secure connection!  
Thanks

 ![Duplicate id](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/7/5772d242a5e7dac59fe85ce09f016a0813d94064.png)  
 ![Peer missing](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/1/f1cc302c4073db701f8c95073c555b2eb1835cd9.png)  
(upload://cg1dj1bXLLZ3CCQlOo8Ri9vpQWR.png)

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [March 21, 2025, 7:40am UTC](https://forum.inductiveautomation.com/t/redundancy-not-working-with-docker-standard-example/103993/2 "2025-03-21T07:40:39Z")

</div>

Duplicate connection to what ? Are the 2 nodes of the redundancy the only gateways in your gateway network ?

This issue happens when two gateways in a network have the same name. Make sure to have different names for the master and backup nodes. The backup will automatically take the name of the master once the redundancy is set up, so you don't have to worry about addressing remote tag providers and things like that from a third gateway.  
You'll be able to tell the 2 gateways apart because " - master" and " - backup" are suffixed to the gateway name.

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [March 21, 2025, 6:15pm UTC](https://forum.inductiveautomation.com/t/redundancy-not-working-with-docker-standard-example/103993/3 "2025-03-21T18:15:23Z")

</div>

You didn't mention what example you're working with. It kind of looks like you might be using the "standard" architecture from here?

> **[GitHub - thirdgen88/ignition-examples: Ignition Examples with Docker Compose](https://github.com/thirdgen88/ignition-examples)**
>
> Ignition Examples with Docker Compose

If so, you might take a backup (if applicable) and try shutting down the stack with `-v` flag to remove the volumes and bring it back up. Past that, you'd need to share what changes you've made to the base configuration. A quick spool up of this solution on my side seems to have the gateways come up as expected.

---

<div class="post-metadata">

**Author:** ![mohamad.tayara](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mohamad.tayara](https://forum.inductiveautomation.com/u/mohamad.tayara)\
**Post date:** [March 21, 2025, 6:35pm UTC](https://forum.inductiveautomation.com/t/redundancy-not-working-with-docker-standard-example/103993/4 "2025-03-21T18:35:08Z")

</div>

It was a volume naming issue! both gw containers were pointing to the same volume which caused the problem! thanks