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 only have certain tests use proxies then you should make sure your PAC file returns the correct proxy (or no proxy) for that particular test's URL.
The tests that support proxies are:
The following tests will attempt to run if set up but they don't explicitly support proxies:
ICMP and TCP pings (including pings included in the predefined web server test):
If you have enabled a proxy on your network, the sensor will, by default not attempt to do ICMP and TCP pings for services that require a proxy. Enable the
Force ICMP pings and
Force TCP pings options to override this behavior.
Unexpected captive portal or proxy
If we have a proxy[like zscaler] configured in the network, it will 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 is effective:
curl https://cdn.capenetworks.io/auth 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 either needs to:
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 being performed on the network, and any errors around external network access will not be shown: