-
Notifications
You must be signed in to change notification settings - Fork 7k
[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.
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
base: production
Are you sure you want to change the base?
Conversation
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryClarified the usage of connectivity.cloudflareclient.com in the WARP tunnel documentation.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
- `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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`connectivity.cloudflareclient.com` is used internally by WARP and should not be used in firewall policies. | |
Thought it may be visible in `warp-diag` and other logs, `connectivity.cloudflareclient.com` is used internally by WARP and should not be used in firewall policies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@samin-cf maybe something like this to acknowledge that it could be visible to customers, I feel like this particualr hostname has been brought up a lot in troubleshooting.
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Preview URL: https://509e99a5.preview.developers.cloudflare.com Files with changes (up to 15) |
Summary
PCX-12866
closes #16062
Screenshots (optional)
Documentation checklist