# 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:** 1\ **Showing post:** 2
**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? --- _[View the full topic](https://forum.inductiveautomation.com/t/getting-signed-out-of-gw-webpage-when-hosting-multiple-gateways-w-docker/113929)._