Where to configure Essentials to allow connections to public URLs?
We have a new Essentials site (4.13.3) that will replace our production site as soon as possible.
For our public-facing maps, we have proxies (publicly available) that point to our internal REST services to enable public access. For some reason the new Essentials installation doesn't allow me to make any connections to these public REST services, but I can access them using the internal URL with the full path w/ domain name etc.
The server itself allows me to browse to those public URLS, so it seems to be an issue with how Essentials is configured.
Have tried adding trusted servers and similar things in the 'Security & Data' section.
Not sure where to go about opening up Essentials to access these URLs. We have a dev environment (also 4.13.3) on a similarly configured server and GE version that doesn't have this issue.
May be a question for our systems people but since it only seems to be an issue working in Essentials I figured I'd ask and see if there are any semi-hidden config settings to allow this within GE.
Thanks
Allen
0
-
Do you get error messages?
TLS 1.2 issue?0 -
Thanks Nico - No errors, just the 'Connection Failed' in red. I've tried looking in the developer tools to find ore details, but no luck there. Looking into TLS 1.2 and .NET versions now 0
Please sign in to leave a comment.
Comments
2 comments