Skip to content

[CF1] clarity on usage for connectivity.cloudflareclient.com #23440

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 14, 2025
Merged

[CF1] clarity on usage for connectivity.cloudflareclient.com #23440

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
509e99a
[CF1] clarity on usage for connectivity.cloudflareclient.com
deadlypants1973 Jul 3, 2025
e39bbbf
Update src/content/docs/cloudflare-one/connections/connect-devices/wa…
deadlypants1973 Jul 7, 2025
31da1d5
Apply suggestions from code review
deadlypants1973 Jul 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions ...nt/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,12 +91,15 @@ The client connects to the following destinations to verify general Internet con

### Inside tunnel

The client connects to the following destinations to verify connectivity inside of the WARP tunnel. Because this check happens inside of the tunnel, you do not need to add these IPs and domains to your firewall allowlist. However, since the requests go through Gateway, ensure that they are not blocked by a Gateway HTTP or Network policy.
The client connects to the following IPs to verify connectivity inside of the WARP tunnel:

- `connectivity.cloudflareclient.com`
- `162.159.197.4`
- `2606:4700:102::4`

Because this check happens inside of the tunnel, you do not need to add these IPs and domains to your firewall allowlist. However, since the requests go through Gateway, ensure that they are not blocked by a Gateway HTTP or Network policy.

`connectivity.cloudflareclient.com` is used internally by WARP and should not be used in firewall policies.

## NEL reporting (optional)

The WARP client reports connectivity issues to our NEL endpoint via `a.nel.cloudflare.com`. This is not technically required to operate but will result in errors in our logs if not excluded properly.
Expand Down