Once a proxy has been configured for your network (on the dashboard), it will affect all tests (external and internal) configured for that same network.
If you want to have only certain tests use proxies, then you should ensure your PAC file returns the correct proxy (or no proxy) for that particular test's URL.
The tests that support proxies are:
HTTP GET
HTTPS GET
Dropbox Throughput
YouTube Download
Zap
The following tests will attempt to run if set up, but they don't explicitly support proxies:
iPerf2
iPerf3
Telnet
ICMP and TCP Pings (including pings part of predefined Web Server test)
If you have enabled a proxy on your network, the sensor will, by default, not attempt to perform ICMP and TCP pings for services that require a proxy. Enable the Force ICMP pings and Force TCP pings options to override this behavior.
Path Analysis and Proxies
Because the Path Analysis feature is based on ICMP, TCP, and UDP packets, it inherently does not support a proxy. As a result, if a network is configured to use a proxy, the Path Analysis trace routes will not execute unless the Force ICMP pings and Force TCP pings flags are set.
If the target URL is inaccessible unless accessed through a proxy, even with the Force ICMP/TCP pings flags set, the test will still fail.
Unexpected Captive Portal or Proxy
If a proxy (like Zscaler) is configured in the network, it may interfere with the sensor's communication with the UXI cloud. An unexpected captive portal or proxy means the sensor gets redirected to an unexpected page when it attempts to communicate with the UXI cloud backend through a particular network. The operation effective in this scenario is:
bashCopy codecurl https://cdn.capenetworks.io/auth
This is where the sensor asserts it has connectivity to the UXI cloud.
If there is a firewall, SSL inspection appliance, or a proxy between the device and our endpoint, it will not be able to communicate with our cloud over that particular network, and it will fail its external connectivity tests.
The customer has the following options:
Add a bypass rule to their Zscaler proxy to allow all our required URLs.
Configure the proxy for the sensor accordingly in the network settings for the sensor.
Disable the network's external connectivity setting, which will stop any external tests from being performed on the network, and any errors around external network access will not be shown.
