You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation states that connectivity.cloudflareclient.com performs a check inside the WARP tunnel, and therefore does not need to be whitelisted on the firewall.
However, we are seeing thousands of requests to connectivity.cloudflareclient.com in the logs of our corporate proxy server, implying that connections are following the system proxy settings and are not going through the WARP tunnel all of the time.
This has been observed both in full WARP and DoH-only modes.
Please can the expected behaviour be clarified? Should we add connectivity.cloudflareclient.com to our PAC file to force it to bypass the proxy server?
Additional information
No response
The text was updated successfully, but these errors were encountered:
Existing documentation URL(s)
https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#connectivity-check
What changes are you suggesting?
The documentation states that
connectivity.cloudflareclient.com
performs a check inside the WARP tunnel, and therefore does not need to be whitelisted on the firewall.However, we are seeing thousands of requests to
connectivity.cloudflareclient.com
in the logs of our corporate proxy server, implying that connections are following the system proxy settings and are not going through the WARP tunnel all of the time.This has been observed both in full WARP and DoH-only modes.
Please can the expected behaviour be clarified? Should we add
connectivity.cloudflareclient.com
to our PAC file to force it to bypass the proxy server?Additional information
No response
The text was updated successfully, but these errors were encountered: