-
Notifications
You must be signed in to change notification settings - Fork 10k
[CF1] Access and tunnels with public hostnames callout #23530
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
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 SummaryUpdated documentation to clarify the use of public hostnames with Cloudflare Tunnel, emphasizing that an Enterprise Cloudflare Access plan is not required for exposure.
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 |
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
Preview URL: https://83f37dd6.preview.developers.cloudflare.com Files with changes (up to 15) |
|
|
||
| :::note | ||
|
|
||
| You do not need a paid Cloudflare Access plan to expose a public hostname via Cloudflare Tunnel. A Cloudflare Tunnel can route traffic to a public hostname without requiring an Access. Access licensing is only required if you want to [secure your public hostname with Cloudflare Access](/cloudflare-one/applications/non-http/infrastructure-apps/) rules, such as requiring users to log in via an identity provider, or protect the hostname with Access policies and identity-based authentication. |
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.
Can we make it more clear that "securing your public hostname" is still possible on a Free account?
src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx
Outdated
Show resolved
Hide resolved
…outing-to-tunnel/index.mdx
src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx
Outdated
Show resolved
Hide resolved
…outing-to-tunnel/index.mdx Co-authored-by: ranbel <[email protected]>
) * [CF1] Access and tunnels with public hostnames callout * wording * Update src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx * Update src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx Co-authored-by: ranbel <[email protected]> --------- Co-authored-by: ranbel <[email protected]>
* [CF1] Access and tunnels with public hostnames callout * wording * Update src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx * Update src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx Co-authored-by: ranbel <[email protected]> --------- Co-authored-by: ranbel <[email protected]>
Summary
PCX-17972
Documentation checklist