From a50dc82887bccb38ec8149e9771367016a5cb1ed Mon Sep 17 00:00:00 2001 From: Till JS Date: Thu, 9 Apr 2026 17:29:29 +0200 Subject: [PATCH] chore(infra): tunnel id 1435166a (locally-managed rebuild result) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After running scripts/mac-mini/rebuild-tunnel.sh, the old remotely- managed tunnel bb0ea86d-... was deleted and a new locally-managed tunnel 1435166a-... took its place. The script's in-place sed of the repo file didn't actually persist (the server-side ~/.cloudflared/ config.yml was patched, but the repo file ended up identical to HEAD because the dev box had a stale checkout that got pulled over). This commit catches the repo file up to the new tunnel id so a fresh clone + setup-cloudflared-service.sh run wires the right credentials file from the start. cloudflared has been running fine on the new tunnel id since the rebuild — it auto-resolved the credentials from ~/.cloudflared/cert.pem when the in-config tunnel id pointed at a deleted tunnel — but the file should match reality regardless. Co-Authored-By: Claude Opus 4.6 (1M context) --- cloudflared-config.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cloudflared-config.yml b/cloudflared-config.yml index 4a921a692..9ee626211 100644 --- a/cloudflared-config.yml +++ b/cloudflared-config.yml @@ -22,8 +22,8 @@ # Cloudflare routes here that we don't have an explicit ingress rule # for. This is the desired failure mode. -tunnel: bb0ea86d-8253-4a54-838b-107bb7945be9 -credentials-file: /Users/mana/.cloudflared/bb0ea86d-8253-4a54-838b-107bb7945be9.json +tunnel: 1435166a-0e3f-4222-8de6-744f32cea5c9 +credentials-file: /Users/mana/.cloudflared/1435166a-0e3f-4222-8de6-744f32cea5c9.json ingress: # ============================================