Sometimes tunnel problems are not really routing problems. They are credential problems wearing a routing costume.

This note came from one of those cases.

The Repair Pattern

The first thing I did was upgrade the binary:

1

sudo cloudflared upgrade

Then I reauthenticated:

1

sudo cloudflared tunnel login

That refreshed the origin certificate and made it possible to inspect and create tunnels again:

1
2

sudo cloudflared tunnel list
cloudflared tunnel create dev-cluster-germany

Why This Matters

Tunnel issues can tempt you into debugging DNS, ingress, or service routing immediately. But if the local cloudflared state is stale or the credentials are no longer right, you are working on the wrong layer.

That is why I like this note. It preserves the simple operational truth:

  • upgrade the client
  • refresh the auth state
  • inspect existing tunnels
  • create or replace credentials cleanly

Before doing anything more elaborate.