-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[CF1] locally managed tunnel update instructions #21169
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,9 +9,9 @@ import { TabItem, Tabs, Render } from "~/components"; | |
|
|
||
| Updates will cause `cloudflared` to restart which will impact traffic currently being served. You can perform zero-downtime upgrades by using Cloudflare's [Load Balancer product](/cloudflare-one/connections/connect-networks/downloads/update-cloudflared/#update-with-cloudflare-load-balancer) or by using [multiple `cloudflared` instances](/cloudflare-one/connections/connect-networks/downloads/update-cloudflared/#update-with-multiple-cloudflared-instances). | ||
|
|
||
| ## Remotely-managed tunnels | ||
| ## Remotely and locally-managed tunnels | ||
|
|
||
| To update `cloudflared` for a tunnel [created through the dashboard](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/): | ||
| To update `cloudflared` for a [remotely-managed tunnel](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/) created through the dashboard or a [locally-managed tunnel](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/): | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For locally-managed tunnels, the instructions below only apply if the tunnel runs as a service. https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/as-a-service/ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think we need to mention locally or remotely managed tunnels here. This is simply an instruction on how to update cloudflared, which is analogous for both. |
||
|
|
||
| <Tabs> <TabItem label="Windows"> | ||
|
|
||
|
|
@@ -92,12 +92,13 @@ sudo systemctl restart cloudflared.service | |
|
|
||
| </TabItem> <TabItem label="Docker"> | ||
|
|
||
| 1. In Zero Trust, go to **Networks** > **Tunnels**. | ||
| 2. Select your tunnel and select **Configure**. | ||
| 3. Select **Docker** and copy the installation command shown in the dashboard. | ||
| 4. Paste this command into a terminal window. | ||
| Run the following command: | ||
|
|
||
| ```sh | ||
| docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <token> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To ensure the command runs with the latest cloudflared it needs to use the flag |
||
| ``` | ||
|
|
||
| This creates a new container from the latest `cloudflared` image. You can now delete the old container. | ||
| This command creates a new container from the latest `cloudflared` image. You can now delete the old container. | ||
|
|
||
| </TabItem> <TabItem label="Other"> | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.