Hyperlint Automation: Broken Link Fixes #19652
Conversation
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?s=60&v=4){kind=small}
|
|
||
| - Captive portals that intercept all DNS traffic will block WARP's [DoH connection](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#overview). Users will likely see a [CF_NO_NETWORK](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_no_network) error after they login to the captive portal. | ||
| - Captive portals that only allow HTTPS traffic will block WARP's [Wireguard UDP connection](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#overview). Users will likely see a [CF_HAPPY_EYEBALLS_MITM_FAILURE](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_happy_eyeballs_failure) error after they login to the captive portal. | ||
| - Captive portals that only allow HTTPS traffic will block WARP's [Wireguard UDP connection](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#overview). Users will likely see a [CF_HAPPY_EYEBALLS_MITM_FAILURE](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_happy_eyeballs_mitm_failure) error after they login to the captive portal. |
There was a problem hiding this comment.
This page: http://localhost:1111/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals/
has a broken internal link to: http://localhost:1111/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/.
The fragment cf_happy_eyeballs_failure does not exist.
By looking at the page: http://localhost:1111/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/
The best fragment to use seems to be: {replacement}
There was a problem hiding this comment.
@bllchmbrs The comment is correct, but there's still a placeholder in the comment that we should probably fix:
The best fragment to use seems to be: {replacement}
There was a problem hiding this comment.
yup, saw this and already fixed! I also plan on fixing the links, just haven't gotten there yet!
| ## 7. Test the connection | ||
|
|
||
| You can now SSH to the GCP server through the new `ssh_app.<zone>` hostname. For instructions on how to connect, refer to our [SSH guide](/cloudflare-one/connections/connect-networks/use-cases/ssh/#2-connect-as-a-user). | ||
| You can now SSH to the GCP server through the new `ssh_app.<zone>` hostname. For instructions on how to connect, refer to our [SSH guide](/cloudflare-one/connections/connect-networks/use-cases/ssh/). |
There was a problem hiding this comment.
This page: http://localhost:1111/cloudflare-one/connections/connect-networks/deploy-tunnels/deployment-guides/ansible/
has a broken internal link to: http://localhost:1111/cloudflare-one/connections/connect-networks/use-cases/ssh/.
The fragment 2-connect-as-a-user does not exist.
By looking at the page: http://localhost:1111/cloudflare-one/connections/connect-networks/use-cases/ssh/
There was no ideal replacement found and so we removed the header link.
|
|
||
| 1. [Deploy the WARP client](/cloudflare-one/connections/connect-devices/warp/deployment/) on your devices in Gateway with WARP mode. | ||
| 2. [Enable the Gateway proxy for TCP](/cloudflare-one/policies/gateway/proxy/#enable-the-gateway-proxy). | ||
| 2. [Enable the Gateway proxy for TCP](/cloudflare-one/policies/gateway/proxy/#turn-on-the-gateway-proxy). |
There was a problem hiding this comment.
This page: http://localhost:1111/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/
has a broken internal link to: http://localhost:1111/cloudflare-one/policies/gateway/proxy/.
The fragment enable-the-gateway-proxy does not exist.
By looking at the page: http://localhost:1111/cloudflare-one/policies/gateway/proxy/
The best fragment to use seems to be: {replacement}
| 2. Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel. | ||
|
|
||
| 3. [Enable the Gateway proxy](/cloudflare-one/policies/gateway/proxy/#enable-the-gateway-proxy) for TCP and UDP. | ||
| 3. [Enable the Gateway proxy](/cloudflare-one/policies/gateway/proxy/#turn-on-the-gateway-proxy) for TCP and UDP. |
There was a problem hiding this comment.
This page: http://localhost:1111/cloudflare-one/connections/connect-networks/private-net/cloudflared/private-dns/
has a broken internal link to: http://localhost:1111/cloudflare-one/policies/gateway/proxy/.
The fragment enable-the-gateway-proxy does not exist.
By looking at the page: http://localhost:1111/cloudflare-one/policies/gateway/proxy/
The best fragment to use seems to be: {replacement}
| 1. Update the **1.1.1.1** app to version 6.29 or above. The update ensures that 1.1.1.1 can [co-exist](#what-to-do-with-the-old-app) with the new Cloudflare One Agent app. | ||
|
|
||
| 2. If you have enabled [TLS decryption](/cloudflare-one/policies/gateway/http-policies/tls-decryption/), ensure that you have a [Do Not Inspect policy](/cloudflare-one/policies/gateway/initial-setup/http/#bypass-inspection-for-incompatible-applications) in place for the following applications: | ||
| 2. If you have enabled [TLS decryption](/cloudflare-one/policies/gateway/http-policies/tls-decryption/), ensure that you have a [Do Not Inspect policy](/cloudflare-one/policies/gateway/initial-setup/http/) in place for the following applications: |
There was a problem hiding this comment.
This page: http://localhost:1111/cloudflare-one/connections/connect-devices/warp/download-warp/cloudflare-one-agent-migration/
has a broken internal link to: http://localhost:1111/cloudflare-one/policies/gateway/initial-setup/http/.
The fragment bypass-inspection-for-incompatible-applications does not exist.
By looking at the page: http://localhost:1111/cloudflare-one/policies/gateway/initial-setup/http/
There was no ideal replacement found and so we removed the header link.
Deploying cloudflare-docs with
|
| Latest commit: |
2d08f70
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fc12e47b.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://hyperlint-scan-broken-link-1.cloudflare-docs-7ou.pages.dev |
workers-devprod
added
the
contribution
|
Congratulations @Hyperlint-AI[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm6ox02pq61560cjvdlcxolx0 This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
4 participants
Broken Link Fix Proposal(s)
The goal of this pull request is to fix broken links in the documentation.
Proposing changes to the following files:
to edit this branch locally, run:
🗣️Leave us feedback
This pull request is part of a series of Hyperlint Automations to ease the burden of maintaining documentation.
We'll be introducing this automation, and others, over the coming months. These automations will always open pull requests(or issues) prior to making changes.
If this is not the change you want, please close this pull request and let us know what you'd like to see.
This feature may introduce erroneous changes (although we work hard to make sure that doesn't happen). Please review the changes before merging.
❌ Limitations:
At this time, Hyperlint can't respond to pull requests or issues.
📩 Need Help?
Please reach out to support with any requests, questions, or concerns.