cloudflare / cloudflare/cloudflared

🐛 Updating with multiple cloudflared instances instructions lacking

Open
#887 3 comments 0 reactions 0 assignees View on GitHub
Confirmed Priority: Normal Type: Documentation
Dominant language
Go
Stars
15.6k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
On the documents page https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/installation it lists an option to `Updating with multiple cloudflared instances` with the following instructions

> If you are not using Cloudflare’s Load Balancer, you can use multiple instances of cloudflared to update without the risk of downtime.
>
> 1. Install a new instance of cloudflared and [create](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/) a new Tunnel.
> 2. Configure the instance to point traffic to the same locally-available service as your current, active instance of cloudflared.
> 3. In the Cloudflare DNS dashboard, [replace](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/routing-to-tunnel/dns/) the address of the current instance of cloudflared with the address of the new instance. Save the record.
> 4. Remove the now-inactive instance of cloudflared.

Step 2 `Configure the instance to point traffic to the same locally-available service as your current, active instance of cloudflared` does not seem to be possible. I believe it is saying to, in the New Tunnel I created in Step 1, create the same routing addresses, which is a lot when you have multiple addresses, but when done returns the error
```
Error: An A, AAAA, or CNAME record with that host already exists. For more details, refer to .
```
To complete the setup I need to create a new subdomain. But even when I do I then attempt to follow Step 3 `In the Cloudflare DNS dashboard, replace the address of the current instance of cloudflared with the address of the new instance. Save the record.` Which seems to be saying I need to go to the Regular Dashboard not the Zero Trust dashboard, as there is no DNS dashboard there. Assuming that to be correct, as it is the closest I can find, I select the domain, select `DNS` > `[Records]`, edit the CNAME record that I created, copy the `Target` & replace the `Target` in the other DNS subdomains. But the new subdomain does not appear in the Zero Trust dashboard for me to route, they do not connect to the location of the original one, they lead to a generic
```
This SUB.ADDRESS.EXT page can’t be found
No webpage was found for the web address: https://SUB.ADDRESS.EXT/
HTTP ERROR 404
```
Even after step 4, removing the other one, it does not work

**Environment and versions**
- OS: Windows & Debian 11
- Architecture: AMD64 Intel
- Version: `2022.12.1 (built 2022-12-20-1252 UTC)` (Windows) & `2023.1.0 (built 2023-01-16-0850 UTC)` Debian

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.