Just ran into this bug again on the latest cloudflared (2025.4.0). Deleting `~/.cloudflared` fixed it, but this shouldn't have required human intervention.
Just ran into this bug again on the latest cloudflared (2025.4.0). Deleting `~/.cloudflared` fixed it, but this shouldn't have required human intervention.