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.
Exact message you may see
Argo Tunnel errorCloudflare Tunnel error
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
- Check cloudflared status and logs
- Re-route DNS to the current tunnel ID
- Allow outbound 7844 TCP/UDP
Detailed fix by platform
Shell
- 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
- Connector — cloudflared running/healthy?
- DNS — CNAME target tunnel ID matches?
- 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:
Similar errors
Most viewed in Cloudflare
Other ways to find it
Where this error sits
Origin: Edge & web server. Errors that are often confused with or caused by this one (click to open):
🧠 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.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 12 Oct 2026