ArcGIS Pro / Live Traffic / Forward Proxy Data Update Issues

dky

Hi, 

Environment:

• Windows 10 Enterprise LTSC, ArcGIS Pro 3.6
• Network Dataset configured with Live Traffic from TomTom
• Internet connectivity via forward proxy

Summary: The live traffic data update functionality in a network dataset in ArcGIS Pro and Enterprise does not appear to use the forward proxy configured in Windows.

 

Details: I’m trying to get the data updates functionality for a network dataset configured with TomTom live traffic. In my test environment (which has no forward proxy), everything works. However, at the client site where all internet-bound communications must pass through a forward proxy, none of the functionality works.

At the client site, running the “BuildOpenLR Cache” geoprocessing tools returns “Failed to download traffic data for building the OpenLR locations cache” error message. I also tried the “Update Traffic Data” and “Update Traffic Incidents” geoprocessing tools – all of which fails but the error messages were less useful.

At the client site, the traffic tab in the network dataset properties also indicates “Last update failed”.

My client’s network requires all internet-bound traffic must flow through their forward proxy. We’re pretty sure the workstation is configured correctly as other ArcGIS Pro functionality (i.e.: basemaps from ArcGIS Online) work fine; it’s just the network analyst functionality that fails when there’s a (forward) proxy. The ArcGIS Pro diagnostic logs indicates DNS resolution failures for the live traffic-related functionality with the following error messages:

Exception was thrown while downloading file 'https://cert-traffic.tomtom.com/tsq/hdf-detailed/xyz-xyz _DETAILED-OPENLR/xyzxyzx/content.proto?flowType=nff': 'resolve: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server [system:11002 at C:\ArcGIS\.esri-packages\boost.17.8.3\include\boost\asio\detail\resolver_service.hpp:84:5 in function 'resolve']'

 

There’s nothing wrong with our DNS server, so we looked into this with WireShark: For basemaps from ArcGIS Online, ArcGIS Pro properly tunnels requests through the client’s proxy server. However, for live traffic data updates, we see ArcGIS Pro first attempting to resolve the DNS entry for the TomTom Live Traffic data endpoint instead of establishing a tunnel with the configured forward proxy server.

We’re able to reproduce this reliably.  

 

We noticed this exact same problem has also been reported previously here but without any response:
https://community.esri.com/t5/arcgis-network-analyst-questions/how-to-set-proxy-for-updatetraffic/m-p/1535822/highlight/true#M8850

 

Has anyone else seen this before? Any thoughts?

 

 

Thanks,

Derek

FrankK

OpenLR live traffic workflow do not currently support environments that require a forward proxy. While other areas of ArcGIS Pro honor the configured forward proxy, the OpenLR update workflow uses a different networking stack to support authorization across the products \ operating systems, and this stack does not currently support forward proxy scenarios. This is a known limitation and is tracked as backlog work.

As a possible workaround, you can create or update the OpenLR cache on a machine running ArcGIS Pro that has direct internet access (that is, does not require a forward proxy), and then copy or share the resulting cache files to a location accessible by the network datasets that require them.