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 endpoint api.cloudflareclient.com is not mentioned anywhere in the WARP zero trust documentation, even though the WARP client seems to connect to this on a regular basis.
This has been observed both in full WARP and DoH-only modes.
Connections to api.cloudflareclient.com follow the system proxy settings, as these connections were observed when reviewing the corporate proxy server logs for a laptop using the WARP zero trust client.
As far as I can tell, api.cloudflareclient.com resolves to generic Cloudflare addresses rather than dedicated WARP ranges.
What is the purpose of api.cloudflareclient.com? Is it supposed to follow the system proxy settings? Do we need to whitelist it?
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/#client-orchestration-api
What changes are you suggesting?
The endpoint
api.cloudflareclient.com
is not mentioned anywhere in the WARP zero trust documentation, even though the WARP client seems to connect to this on a regular basis.This has been observed both in full WARP and DoH-only modes.
Connections to
api.cloudflareclient.com
follow the system proxy settings, as these connections were observed when reviewing the corporate proxy server logs for a laptop using the WARP zero trust client.As far as I can tell,
api.cloudflareclient.com
resolves to generic Cloudflare addresses rather than dedicated WARP ranges.What is the purpose of
api.cloudflareclient.com
? Is it supposed to follow the system proxy settings? Do we need to whitelist it?Additional information
No response
The text was updated successfully, but these errors were encountered: