# Web config/perspective logout when gateways are on the same IP

**URL:** <https://forum.inductiveautomation.com/t/web-config-perspective-logout-when-gateways-are-on-the-same-ip/45520>\
**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:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\
**Post date:** [April 13, 2021, 8:18am UTC](https://forum.inductiveautomation.com/t/web-config-perspective-logout-when-gateways-are-on-the-same-ip/45520/1 "2021-04-13T08:18:47Z")

</div>

While using Google Chrome, is someone else experiencing logout while navigating between web-gateway configs.

It happends to me while using dockerized setup.

For example, while trying to compare/copy settings between `<myIpAdress>:8088/web/config` and `<myIpAdress>:8089/web/config`. I always have to log in again when switching tabs. Then when navigating back I have to log in again.

As a side note: when using perspective, the sessions does not get disconnected, but some buttons (with security) will not work untill I login again

---

<div class="post-metadata">

**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")

</div>

> [@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 …

---

<div class="post-metadata">

**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\
**Post date:** [April 13, 2021, 11:48am UTC](https://forum.inductiveautomation.com/t/web-config-perspective-logout-when-gateways-are-on-the-same-ip/45520/3 "2021-04-13T11:48:31Z")

</div>

Thank you!

I was thinking that i might have been a bug, which is why I posted this. But that hostfile edit seems sufficient for development purposes.