Skip to content

Commit 6f8ee2e

Browse files
authored
change cloudflare one domain
1 parent b9898a9 commit 6f8ee2e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

cmd/cloudflared/tunnel/cmd.go

+1-1
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ then protect with Cloudflare Access).
162162
B) Locally reachable TCP/UDP-based private services to Cloudflare connected private users in the same account, e.g.,
163163
those enrolled to a Zero Trust WARP Client.
164164
165-
You can manage your Tunnels via dash.teams.cloudflare.com. This approach will only require you to run a single command
165+
You can manage your Tunnels via one.dash.cloudflare.com. This approach will only require you to run a single command
166166
later in each machine where you wish to run a Tunnel.
167167
168168
Alternatively, you can manage your Tunnels via the command line. Begin by obtaining a certificate to be able to do so:

cmd/cloudflared/tunnel/teamnet_subcommands.go

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ func buildRouteIPSubcommand() *cli.Command {
3232
UsageText: "cloudflared tunnel [--config FILEPATH] route COMMAND [arguments...]",
3333
Description: `cloudflared can provision routes for any IP space in your corporate network. Users enrolled in
3434
your Cloudflare for Teams organization can reach those IPs through the Cloudflare WARP
35-
client. You can then configure L7/L4 filtering on https://dash.teams.cloudflare.com to
35+
client. You can then configure L7/L4 filtering on https://one.dash.cloudflare.com to
3636
determine who can reach certain routes.
3737
By default IP routes all exist within a single virtual network. If you use the same IP
3838
space(s) in different physical private networks, all meant to be reachable via IP routes,

0 commit comments

Comments
 (0)