Select to view content in your preferred language

IIS Configuration for a custom Websocket URL

169
0
03-24-2026 06:00 PM
JazHamilton36
New Contributor

We have a Stream Server URL which has a internal computer name (FQDN) in it, which is reachable while on internal network, but not when accessing web apps from outside the typical network. We use Entra ID application proxy to sign in and access apps from outside the work network. The Stream Server layer drops out of apps as the FQDN isn't accessible via this external access mode.   


There's a "WebSocketContextURL" property that can be set to our domain of 'https://maps.fireandemergency.nz/' , and the streaming service adopts this domain into its URL with no issue, but I believe from looking at old community post on this topic that there's extra config required after this setting is made, within IIS. Without that extra config, ArcGIS Pro and other applications like ArcGIS Web Maps can 'see' the Streaming Service, but no data comes through. Seems like the protocol doesn't switch? Lots of Subscribe calls that retry. 

What's going on after I set the "WebSocketContextURL" for IIS, and what settings need to be altered for the IIS / Web Server to pass out or handle wss connections?  

We're running 11.3 ArcGIS Server/GeoEvent Server, and Web Adaptor with IIS on a separate machine. 

0 Kudos
0 Replies