Symptoms
You Cannot connect to a HTML5 session externally via UAGUsers receive the error "Failed to resolve proxying route for request" when using Blast with VMware Unified Access Gateway.You have the blast secure gateway enabled on your connection server.
This issue can be seen in the bsg.log on the UAG Appliance.Reference: Collecting Logs from the Unified Access Gateway ApplianceSample Log Line of an Incorrect Configuration:
[2022-11-16 19:33:30.668] [INFO] 7304 [absg-master] - Added route D6D23E36-*** to target 192.168.0.201|8443
Note:
The IP address and port in the above Logline matches a broker IP and port. When you see the target as the Connection Server IP and a port of 8443 this is wrong and an indication that the BSG gateway is enabled on the Connection Server.
Sample Log Line of a Correct Configuration:When the Blast Secure Gateway is disabled on the Connection Server, the log line you see in bsg.log indicates a route being prepared to the virtual desktop or RDS host address on port 22443 as seen here. This is correct.
[2022-11-17 16:42:10.603] [INFO] 7304 [absg-master] - Added route C425F277-*** to target 192.168.0.36|22443
Purpose
To highlight a common product misconfiguration.
Cause
The tunnel option for Blast is selected both on the UAG and the connection server.Blast Secure Gateway does not support multihop BSG.
Resolution
Procedure:
In Horizon Administrator, select View Configuration > Servers.On the Connection Servers tab, select a Connection Server instance and click Edit.Disable the use of the Blast Secure Gateway or Select "Use Blast Secure Gateway for only HTML Access Blast connections to machine"
Reference: Configure the Blast Secure GatewayNote: This option is compatible with UAG, which requires other tunnels to be set on the UAG rather than the broker.
Related Information
When connecting to a Horizon View virtual machine using Blast, the alert "SSL Session is invalid" appears (2088354)
