# Getting signed out of GW webpage when hosting multiple Gateways w/Docker **URL:** \ **Category:** Ignition\ **Tags:** docker\ **Created:** [February 12, 2026, 2:54pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929 "2026-02-12T14:54:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Cade\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cade\_Allen](https://forum.inductiveautomation.com/u/Cade_Allen)\ **Post date:** [February 12, 2026, 2:54pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/1 "2026-02-12T14:54:02Z")
Hi, I’m running multiple Gateways with Docker on my local computer. I have each Gateway mapped to unique ports, but I’ve noticed that when I sign into one Gateway webpage, it signs me out of the other. Additionally, I have to sign in twice to gain access to the webpage. Any thoughts on why this could be happening? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 12, 2026, 3:12pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/2 "2026-02-12T15:12:52Z")
> [@Multiple docker instances on the same host share the same connection](https://forum.inductiveautomation.com/t/multiple-docker-instances-on-the-same-host-share-the-same-connection/37452/2): > > More on this behavior here: It's a function of the webserver not isolating the session authentication cookies per host:ip - only per host. There's a workaround mentioned there, but I wouldn't necessarily recommend it unless you really know what you're doing. If you're developing entirely on the local machine, there should be internal IPs for each container that are unique - something like 172.17.0.X. You can access whatever port on that internal IP, regardless of what the container is set to … I think this changed in 8.3 though? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 12, 2026, 3:18pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/3 "2026-02-12T15:18:04Z")
Actually it may not have changed... I think I was using different hostnames as well as ports when I was in this situation recently. ---
**Author:** ![Cade\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cade\_Allen](https://forum.inductiveautomation.com/u/Cade_Allen)\ **Post date:** [February 12, 2026, 3:35pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/4 "2026-02-12T15:35:17Z")
Looking at that thread, it looks like I need to access the gateways using the internal container IP addresses? I tried this and it doesn’t seem like those IPs are exposed to my host. I’m new to Docker - do I need to change the network interface setup to expose those? Using Docker Desktop on Windows, I can’t ping the container IPs from my host. ---
**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:** [February 12, 2026, 4:20pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/5 "2026-02-12T16:20:44Z")
Supposed to be fixed as of 8.3.2 - independent gateway names even on the same host will get unique cookies. ---
**Author:** ![Craig\_webber](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/craig_webber/32/62546_2.png) [@Craig\_webber](https://forum.inductiveautomation.com/u/Craig_webber)\ **Post date:** [February 13, 2026, 10:15pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/6 "2026-02-13T22:15:02Z")
Haven’t tested it yet on 8.3.2 yet. ive been using multiple chrome profiles for each gateway which does the trick ---
**Author:** ![Cade\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cade\_Allen](https://forum.inductiveautomation.com/u/Cade_Allen)\ **Post date:** [February 16, 2026, 4:35pm UTC](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929/7 "2026-02-16T16:35:23Z")
Turns out the IU videos cover this issue, including the process of adding an entry to the hosts file. I also found that running Docker in Linux allows me to individually access the containers via their IP addresses which is another option. > **[Adding Ignition Gateways Video at Inductive University](https://inductiveuniversity.com/video/adding-ignition-gateways)** > > This lesson will kick off the walkthrough of our testing environment and we'll start by adding our Ignition containers.