Skip to content

[CF1] private IP and BISO limit #22244

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

Merged
merged 4 commits into from
May 7, 2025
Merged

Conversation

deadlypants1973
Copy link
Contributor

Summary

PCX-16607

Screenshots (optional)

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

Copy link
Contributor

hyperlint-ai bot commented May 6, 2025

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 Summary

Updated documentation regarding private IP usage and Browser Isolation compatibility.

  • Clarified that private hostnames are only available over port 443 with valid SNI.
  • Added a note that using private IPs on non-443 ports with Browser Isolation will result in a Gateway block page.
  • Introduced a recommendation to configure a private network application for non-443 port usage.

Modified Files

  • src/content/docs/cloudflare-one/applications/non-http/self-hosted-private-app.mdx
  • src/content/docs/cloudflare-one/policies/browser-isolation/known-limitations.mdx

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 hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

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 hyperlint-ignore to the PR to ignore the link check for this PR.


## Browser Isolation is not compatible with private IPs on non-`443` ports

Browser Isolation is not compatible with [self-hosted private applications](/cloudflare-one/applications/non-http/self-hosted-private-app/) that use private IP addresses on ports other than `443`. Trying to access an application with this configuration will result in a Gateway block page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with self-hosted applications defined by private ips on ports other than 443

@deadlypants1973 deadlypants1973 merged commit 8bd4803 into production May 7, 2025
12 checks passed
@deadlypants1973 deadlypants1973 deleted the kate/fixes-443limit branch May 7, 2025 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants