1033 🟧 Cloudflare

Cloudflare Error 1033: Argo Tunnel error (Cloudflare Tunnel not connected)

The hostname routes to a Cloudflare Tunnel, but no healthy cloudflared connector is running for it.

Seen on: Cloudflare

Meaning

The DNS record points to <tunnel-id>.cfargotunnel.com. If cloudflared stopped, lost its credentials, or the tunnel was deleted/recreated with a new ID, Cloudflare returns 1033.

Common causes

  • cloudflared service stopped/crashed
  • Tunnel deleted or recreated (DNS points to old ID)
  • Credentials file/token missing
  • Network blocking outbound to Cloudflare (port 7844)

⚡ Quick fix

  1. Check cloudflared status and logs
  2. Re-route DNS to the current tunnel ID
  3. Allow outbound 7844 TCP/UDP

Detailed fix by platform

Shell

  1. bash
    cloudflared tunnel list
cloudflared tunnel info my-tunnel
sudo systemctl status cloudflared
cloudflared tunnel route dns my-tunnel app.example.com

How to diagnose

  1. Connector — cloudflared running/healthy?
  2. DNS — CNAME target tunnel ID matches?
  3. Network — Outbound 7844 allowed?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.