"Connection Failed" when trying to add WMS Service Connection
Hey all -
Essentials: 4.12, Viewer HTML5 4.12.1
I'm not sure if this is a Geocortex issue or a server configuration one, but maybe the collective brain has figured it out either way.
I am unable to add a WMS through Manager. The site I am trying to use is from NASA:
https://gibs.earthdata.nasa.gov/wms/epsg3857/best/wms.cgi?
I've tried:
*numerous variations of the URL - REQUEST=GetCapabilities&VERSION=1.1.1&SERVICE=WMS
*verifying our Proxy file settings
*importing the NASA GIBS website certificates into the certificate store for the server on which Geocortex runs
*trying it as an ArcGIS service using one of the pre-defined layers from Esri (https://modis.arcgis.com/arcgis/rest/services/MODIS/ImageServer) - also "Connection Failed"
*adding the service through Manager both on my desktop and directly on the server - no difference
*running developer tools in Chrome during the service addition process - every item shows a 200 status
*running Fiddler during the service addition process - every item shows a 200 status
The real stumper is that those endpoint URLs work fine in ArcMap and Spotfire.
Can someone try to add the NASA Gibs service to Geocortex? And if that works, and it points to a server block, any ideas from the community?
Thanks,
Jena
wms; ogc; 4.12; add map service; service connection; add connection; web map service
0
-
Is TLS 1.2 configured on your server?
https://support.geocortex.com/essentialsGSCkbaDetail?sub-nav=kba&main-nav=essentials&id=kA6f200000091IvCAI0 -
I checked https://gibs.earthdata.nasa.gov with a TLS checker (https://www.cdn77.com/tls-test), only TLS 1.2 is enabled. 0 -
Great ideas from Nico, but alas, still no luck.
Per the support article, I updated our .NET to 4.7 (we were on 4.6) and added the registry keys. Restarted the server, and tried to add the service; still got "Connection Failed". I also tried the TLS 1.2 Esri test services and had the same result (although those added fine in ArcMap). In Fiddler, the "Tunnel to" TextView shows "Version: 3.3 (TLS/1.2)" for the attempted connections, so we seem to be using that protocol, just to no avail.
Other thoughts?0 -
Hi Jena,
That is indeed very bizarre! I know you mentioned trying numerous variations of the URL - did you try this: https://gibs.earthdata.nasa.gov/wms/epsg3857/best/wms.cgi?SERVICE=WMS&REQUEST=GetCapabilities by any chance?
If that still doesn't work, I would suggest submitting a Support case.
Many thanks!
Stephanie0 -
Stephanie -
Alas, I had tried that and a few others. I gave it a shot this morning again, because you never know, but no luck. We're going to try our IT folks first because I have a strong suspicion it's some sort of high-level organizational permission issue, but it they claim otherwise I'll definitely give you a shout.
Thanks :)
Jena0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
5 kommentarer