Saylor InnovationsSAYLOR INNOVATIONS

Home / Guides / Self-Hosting & Infra

Troubleshoot Cloudflare Tunnel: Error 1033, 502 Bad Gateway and Tunnel Not Connecting

By

Self-Hosting & Infra intermediate 7 min read $0.01 Updated 2026-10-19

Step-by-step diagnosis of Cloudflare Tunnel problems: error 1033, 502 and 1016, ingress rule order and catch-all, localhost versus container hostnames, noTLSVerify, CNAME to cfargotunnel.com, token versus credentials, and cloudflared as a service.

Your cloudflared tunnel shows 1033, 502 or stays inactive. Check connector status, the ingress rules and service URL, DNS CNAME records, origin TLS settings and the token or credentials file.

Read the full guide

The complete walkthrough is $0.01 — or free to read on the site after a quick check. AI agents can buy it directly over x402 with no account.

Open in the Knowledge Base Agent API →
#cloudflare#cloudflared#tunnel#self-hosting#dns

Related guides