Multiple Gateway Configuration Logouts

[colin.bonner]

I run a full Redundant Ignition instance with Git integration meaning I have 4 gateways in total; Master, Backup, Dev & Test.

It is quite normal for me to have tabs open to the Gateway Web pages on multiple Gateways, when I log into one gateway it logs the other Gateways i’m connected to out. This is rather frustrating when comparing Gateway settings.

Is this normal or is there something misconfigured? Perhaps a browser setting, cookies etc.

[PGriffith]

It's normal; an unfortunate consequence of things on our webserver. If each session has a different hostname, then you can log in to multiple gateways simultaneously. One recommendation when this last came up was to put in different hosts file entries for each gateway, then always connect to them by hostname.

This thread has more information on that and some other workarounds:

Odd behavior when running multiple 8.0.X Gateways in one PC

This week, after the announcement of Ignition Maker Edition, I downloaded the Windows ZIP installer, and unzipped it into two locations, each with a different purpose; one would be full-fleged Ignition, and the other Maker Edition. Since in my company we are still supporting 7.9, I’ve been doing this ZIP installs for quite some time; having each Gateway registered with its own service name, and configuring all in different ports (HTTP, HTTPS, Metro SSL). Before this week I was only running 7.9…

[colin.bonner]

Hi Paul,
Thanks for your reply. Yeah this makes sense,. I guess it’s more noticeable when you are making lots of changes, such as I was today with upgrades on all gateways.

My setup has all Gateways at different IP addresses however my remote laptop ties them all together as SSH Tunnels, since they are all then bound to localhost then this is clearly the reason.

Modification of the hosts file won’t help I guess but there may be workarounds in your links. Either way, as you say, this normal lol

[jspecht]

@colin.bonner

My setup has all Gateways at different IP addresses however my remote laptop ties them all together as SSH Tunnels, since they are all then bound to localhost then this is clearly the reason.

Modification of the hosts file won’t help I guess but there may be workarounds in your links. Either way, as you say, this normal lol

I'd think the local hosts file modification should work... couldn't you create a hostname for each gateway and map it to the loopback IP 127.0.0.1? Then access each gateway's http url in your browser by its hostname (as defined in your hosts file) and port (the one that is bound by its respective ssh tunnel on localhost).

[colin.bonner]

Correct me if i’m wrong but the hosts file deals with DNS only and cannot deal with ports. For example, the url’s for each of my gateways are:

http://localhost:8090
http://localhost:8091
http://localhost:8092
http://localhost:8093

The hostname is the same for all 4, each one would have to have a different IP in order for the system to resolve the hostname/ip via the hosts file.

[pturmel]

There’s no solution to distinguish ports. The best you could do would be to point a bunch of distinct DNS names at localhost and use them for separate gateways.

[PGriffith]

You could use different loopback IPs on your tunnels:

How to assign a hostname to SSH tunnel

[colin.bonner]

Hi Paul,
Thanks, this was just the trick, I did not know that you could actually stipulate a different loopback address in the ‘Source Port’ section of the Tunnels in PuTTY instead of just a port number.

[cbabb]

Perhaps this isn't the best solution, but it's working for us so far:

For some testing, I have a VM up running Ubuntu... on that I have docker installed and am running 3 gateways and a mysql server... We ran into the exact issue described here with our gateway config pages being logged out any time we switched tabs to the different gateways in our browser.

What I did was add the container names to the Hosts file in windows. For example

192.168.73.80 controlcenter
192.168.73.80 customer1
192.168.73.80 customer2

After that, hitting them with http://controlcenter:9988, for example, we are no longer seeing our gateways being logged out when switching between the gateway pages.