Skip to content

Hyperlint Automation: Broken Link Fixes #19652

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 5 commits into from
Feb 3, 2025
Merged

Hyperlint Automation: Broken Link Fixes #19652

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f79fbce
Fix issue: WorkspaceTaskSubType.BROKEN_LINK
hyperlint-ai[bot] Feb 2, 2025
da5901f
Fix issue: WorkspaceTaskSubType.BROKEN_LINK
hyperlint-ai[bot] Feb 2, 2025
9286114
Fix issue: WorkspaceTaskSubType.BROKEN_LINK
hyperlint-ai[bot] Feb 2, 2025
538eb6d
Fix issue: WorkspaceTaskSubType.BROKEN_LINK
hyperlint-ai[bot] Feb 2, 2025
2d08f70
Fix issue: WorkspaceTaskSubType.BROKEN_LINK
hyperlint-ai[bot] Feb 2, 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
2 changes: 1 addition & 1 deletion ...nnections/connect-devices/warp/configure-warp/warp-settings/captive-portals.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,4 +41,4 @@ If WARP cannot establish a connection to Cloudflare, it will:
- Some public Wi-Fi networks are incompatible with running WARP:

- 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.
Copy link
Contributor Author

@hyperlint-ai hyperlint-ai bot Feb 2, 2025

Choose a reason for hiding this comment

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

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}

Copy link
Contributor

@pedrosousa pedrosousa Feb 3, 2025

Choose a reason for hiding this comment

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

@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}

Copy link
Contributor

@bllchmbrs bllchmbrs Feb 3, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

yup, saw this and already fixed! I also plan on fixing the links, just haven't gotten there yet!

2 changes: 1 addition & 1 deletion ...nnections/connect-devices/warp/download-warp/cloudflare-one-agent-migration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ If you downloaded and installed the 1.1.1.1 app manually, here are the recommend

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:
Copy link
Contributor Author

@hyperlint-ai hyperlint-ai bot Feb 2, 2025

Choose a reason for hiding this comment

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

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.


* *Google Services (Do Not Inspect)*
* *Google Play Store (Do Not Inspect)*
Expand Down
2 changes: 1 addition & 1 deletion ...e-one/connections/connect-networks/deploy-tunnels/deployment-guides/ansible.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -323,4 +323,4 @@ It may take several minutes for the GCP instance and tunnel to come online. You

## 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/).
Copy link
Contributor Author

@hyperlint-ai hyperlint-ai bot Feb 2, 2025

Choose a reason for hiding this comment

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

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.

2 changes: 1 addition & 1 deletion ...dflare-one/connections/connect-networks/private-net/cloudflared/private-dns.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ By default, the WARP client sends DNS requests to [1.1.1.1](/1.1.1.1/), Cloudfla

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.
Copy link
Contributor Author

@hyperlint-ai hyperlint-ai bot Feb 2, 2025

Choose a reason for hiding this comment

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

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}


4. Next, [create a Local Domain Fallback entry](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the WARP client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.

Expand Down
2 changes: 1 addition & 1 deletion ...re-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ import { Tabs, TabItem, Badge, Render } from "~/components";
To connect your devices to Cloudflare:

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).
Copy link
Contributor Author

@hyperlint-ai hyperlint-ai bot Feb 2, 2025

Choose a reason for hiding this comment

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

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}

3. [Create device enrollment rules](/cloudflare-one/connections/connect-devices/warp/deployment/device-enrollment/) to determine which devices can enroll to your Zero Trust organization.

## 3. Route server IPs through WARP
Expand Down