If you are referring to the server using an IP address, then DNS is out of the equation, unless tsnet is internally trying to resolve a DNS name, which it might if signed SSL certificates are involved. If that is the case, then yes, it is out of your control, much like my Forms Generator app, when the local IT at a site has locked down outbound connections to SQL servers, or all DNS queries go through their content management system.
In these cases, knowing the IP of the certificate server (like go daddy or network solutions) would not help as these are usually server farms and the IP address can change moment to moment. DNS is essential. It is possible (though definitely not prescribed) to create a hosts entry for one of the IP addresses of the cert authority, but there is no guarantee that server will be online in the future. Bob S > On Sep 1, 2017, at 13:41 , J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > This is for an Android app that can be run from anywhere, so I don't have > control over the routers or servers. (And yeah, I didn't quite get everything > you were talking about, I'm a network novice.) > > The apps run fine for most people and only get this error with a few users. I > think you're basically saying there's no cure, right? > > If the web site has a static IP and the Android app uses that instead of a > domain name, will that fix it? The app is communicating with a database on > the web server. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
