Plugin not working on lastest version of Geofency

[Guest]

Very curious to know if conected2 is the load balancer or not here too!

[randy]

Rich wrote about it in another thread.

I reset the server, let me know if you are still having an issue.

But just so we are clear, we currently have 2 servers that serve HS connections, they are connected11.homeseer.com and connected22.homeseer.com. Right now only one is active at a time and the other is a backup. You should always connect to connected2.homeseer.com. That is an Azure traffic manager connection and it will route traffic to the correct active server. So when you say that connected2 does not work but connected22 does work, the tells me that your system might be connected to a server that is currently not the active server. Restart your HS system and then try connected2 again. That will tell us if that is the problem. I can tell you that quite a few systems are not honoring the TTL on the DNS for connected2 (the traffic manager uses DNS to direct traffic) and they stay connected to the wrong server.

In any event a change is being tested where we will move to a load balancing arrangement and it won't matter which system you are connected to, we will automatically redirect as needed.

I wonder if the geofency app is caching an IP address? For example if it accesses connected2 and it returns the IP address for connected11 it then saves that IP. If we then switch to connected22 the app should detect this (based on the TTL timeout which is about 15 seconds) and switch to the other IP. If this is an app that you run, next time you see a connection issue restart that app and see if it then works. I know there are systems that are not honoring the TTL. Right now we are on connected22 but I see 13 systems connected to connected11. Those systems will run into issues.