# Web config/perspective logout when gateways are on the same IP **URL:** \ **Category:** Ignition Early Access\ **Created:** [April 13, 2021, 8:18am UTC](https://forum.inductiveautomation.com/t/web-config-perspective-logout-when-gateways-are-on-the-same-ip/45520 "2021-04-13T08:18:47Z")\ **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:** [April 13, 2021, 11:33am UTC](https://forum.inductiveautomation.com/t/web-config-perspective-logout-when-gateways-are-on-the-same-ip/45520/2 "2021-04-13T11:33:22Z")
> [@Multiple docker instances on the same host share the same connection](http://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 … --- _[View the full topic](https://forum.inductiveautomation.com/t/web-config-perspective-logout-when-gateways-are-on-the-same-ip/45520)._