Skip to content

Commit 80fb823

Browse files
committed
update warp-cli commands
1 parent 059ef16 commit 80fb823

File tree

2 files changed

+7
-8
lines changed

2 files changed

+7
-8
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ To enroll your device using the terminal:
3232
3. Enroll into Cloudflare Zero Trust using your organization's <GlossaryTooltip term="team name">team name</GlossaryTooltip>:
3333

3434
```sh
35-
warp-cli teams-enroll <your-team-name>
35+
warp-cli registration new <your-team-name>
3636
```
3737

3838
4. In the browser window that opens, complete the authentication steps required by your organization.
@@ -44,23 +44,23 @@ To enroll your device using the terminal:
4444
6. Verify the registration in the terminal:
4545

4646
```sh
47-
warp-cli account
47+
warp-cli registration show
4848
```
4949

5050
<Details header="Troubleshoot missing registration">
5151

5252
The registration process may take a few minutes to complete. If the registration continues to be missing, then manually copy the authentication token from the browser to the WARP client:
5353

5454
1. On the success page, right-click and select **View Page Source**.
55-
2. Find the HTML metadata tag that contains the token. For example, `<meta http-equiv="refresh" content"=0;url=com.cloudflare.warp://acmecorp.cloudflareaccess.com/auth?token=yeooilknmasdlfnlnsadfojDSFJndf_kjnasdf..." />`
55+
2. Find the HTML metadata tag that contains the token. For example, `<meta http-equiv="refresh" content"=0;url=com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=yeooilknmasdlfnlnsadfojDSFJndf_kjnasdf..." />`
5656
3. Copy the URL field: `com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=<your-token>`
5757
4. In the terminal, run the following command using the URL obtained in the previous step.
5858

5959
```sh
60-
warp-cli teams-enroll-token com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=<your-token>
60+
warp-cli registration token "com.cloudflare.warp://<your-team-name>.cloudflareaccess.com/auth?token=<your-token>"
6161
```
6262

63-
If you get an API error, then the token has expired. Generate a new one by refreshing the web page and quickly grab the new token from the page source.
63+
If you get a `401` error, then the token has expired. Generate a new one by refreshing the web page and quickly grab the new token from the page source.
6464

6565
</Details>
6666

src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector.mdx

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
126126
3. Verify the registration:
127127

128128
```sh
129-
warp-cli account
129+
warp-cli registration show
130130
```
131131

132132
```sh output
@@ -148,7 +148,7 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
148148
```
149149
- Clear an old registration and trigger WARP to re-register:
150150
```sh
151-
sudo warp-cli delete
151+
sudo warp-cli registration delete
152152
```
153153
- Review your [WARP daemon logs](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/) for information about why the registration is failing.
154154

@@ -162,7 +162,6 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
162162

163163
```sh output
164164
Status update: Connected
165-
Success
166165
```
167166

168167
<Details header="Troubleshoot connection">

0 commit comments

Comments
 (0)