Hyperlint Automation: Broken Link Fixes #20645
Conversation
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?s=60&v=4){kind=small}
|
|
||
| - Open a browser window and prompt you to log in to your Cloudflare account. After logging in to your account, select your hostname. | ||
| - Generate an account certificate, the [cert.pem file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#certpem), in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory). | ||
| - Generate an account certificate, the [cert.pem file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#certpem), in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/). |
There was a problem hiding this comment.
We found a broken link on this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/ (This page may or may not be the same as the page on which you find this comment but we found this same link on this page.)
The link is to this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/ but references the fragment default-cloudflared-directory that does not exist.
By looking at the page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/
There was no ideal replacement found and so we removed the header link.
|
|
||
| - Create a tunnel by establishing a persistent relationship between the [name you provide](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#tunnel-name) and a [UUID](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#tunnel-uuid) for your tunnel. At this point, no connection is active within the tunnel yet. | ||
| - Generate a [tunnel credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#credentials-file) in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory). | ||
| - Generate a [tunnel credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/). |
There was a problem hiding this comment.
We found a broken link on this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/ (This page may or may not be the same as the page on which you find this comment but we found this same link on this page.)
The link is to this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/ but references the fragment default-cloudflared-directory that does not exist.
By looking at the page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/
There was no ideal replacement found and so we removed the header link.
|
Howdy and thanks for contributing to our repo. We review 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. |
| ``` | ||
|
|
||
| This will generate a [credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#credentials-file) in `.json` format. | ||
| This will generate a [credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) in `.json` format. |
There was a problem hiding this comment.
We found a broken link on this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/as-a-service/windows/ (This page may or may not be the same as the page on which you find this comment but we found this same link on this page.)
The link is to this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/ but references the fragment credentials-file that does not exist.
By looking at the page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/
There was no ideal replacement found and so we removed the header link.
| | **Scope** | Account-wide | Tunnel-specific | | ||
| | **File type** | `.pem` | `.json` | | ||
| | **Stored in** | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory) | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory) | | ||
| | **Stored in** | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) | |
There was a problem hiding this comment.
We found a broken link on this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/tunnel-permissions/ (This page may or may not be the same as the page on which you find this comment but we found this same link on this page.)
The link is to this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/ but references the fragment default-cloudflared-directory that does not exist.
By looking at the page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/
There was no ideal replacement found and so we removed the header link.
| ## Configuration file | ||
|
|
||
| This is a YAML file that functions as the operating manual for `cloudflared`. `cloudflared` will automatically look for the configuration file in the [default `cloudflared` directory](#default-cloudflared-directory), but you can store your configuration file in any directory. It is recommended to always specify the file path for your configuration file whenever you reference it. By creating a configuration file, you can have fine-grained control over how their instance of `cloudflared` will operate. This includes operations like what you want `cloudflared` to do with traffic (for example, proxy websockets to port `xxxx` or SSH to port `yyyy`), where `cloudflared` should search for authorization (credentials file, tunnel token), and what mode it should run in (for example, [`warp-routing`](/cloudflare-one/connections/connect-networks/private-net/)). In the absence of a configuration file, cloudflared will proxy outbound traffic through port `8080`. For more information on how to create, store, and structure a configuration file, refer to the [dedicated instructions](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/). | ||
| This is a YAML file that functions as the operating manual for `cloudflared`. `cloudflared` will automatically look for the configuration file in the [default `cloudflared` directory](), but you can store your configuration file in any directory. It is recommended to always specify the file path for your configuration file whenever you reference it. By creating a configuration file, you can have fine-grained control over how their instance of `cloudflared` will operate. This includes operations like what you want `cloudflared` to do with traffic (for example, proxy websockets to port `xxxx` or SSH to port `yyyy`), where `cloudflared` should search for authorization (credentials file, tunnel token), and what mode it should run in (for example, [`warp-routing`](/cloudflare-one/connections/connect-networks/private-net/)). In the absence of a configuration file, cloudflared will proxy outbound traffic through port `8080`. For more information on how to create, store, and structure a configuration file, refer to the [dedicated instructions](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/). |
There was a problem hiding this comment.
We found a broken link on this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/tunnel-permissions/ (This page may or may not be the same as the page on which you find this comment but we found this same link on this page.)
The link is to this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/ but references the fragment default-cloudflared-directory that does not exist.
By looking at the page: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/
There was no ideal replacement found and so we removed the header link.
|
CI run failed: build logs |
2 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.