Domain Doctor Diagnostics
Error 52x FixRun automated end-to-end diagnostics to isolate and fix Error 521, 522, 525, 526, 1000, and redirect loops.
📖 Full Explanation
Cloudflare 52x errors can be notoriously frustrating to debug. \1 runs an automated 8-point diagnostic routine testing DNS resolution, origin reachability, TLS handshake compatibility, SSL cipher negotiation, redirect loops, and WAF blocks, pin-pointing the exact cause and fix.
⚙️ Command Options & Flags
| Option / Flag | Description | Default |
|---|---|---|
| --check-origin | Attempt direct TCP probe to origin IP address | true |
| --check-ssl | Verify origin SSL certificate validity and chain | true |
| --json | Output diagnostic findings in JSON format | false |
🔬 Technical Corollary & Edge Mechanics
Bypasses edge proxying to connect directly to the origin server's IP address. Tests whether port 80/443 is open, inspects origin SSL certificate expiration dates and CA validity, and verifies whether Cloudflare's SSL mode (e.g. Strict) matches the origin's capabilities.
🎯 Real-World DevOps Use Cases
Debugging Error 521 (Web Server Is Down)
Determine whether the origin firewall is dropping packets or the web server process crashed.
Resolving Insecure SSL Redirect Loops
Detect when Flexible SSL causes infinite 301 redirect loops between Cloudflare and origin.
💻 Live Output Simulation
$ cflare doctor namishkumar.in 🩺 Running Cloudflare Diagnostic Suite on namishkumar.in... [1/6] DNS Resolution: ✔ OK (Resolves to Cloudflare 104.21.x.x) [2/6] Edge Reachability: ✔ OK (HTTP 200, 18ms TTFB) [3/6] Origin TCP Connectivity: ✖ FAILED (Connection refused on 198.51.100.12:443) [4/6] SSL/TLS Compatibility: ⚠ Warning: Zone is Full (Strict) but origin 443 is closed. 📌 Diagnosis: Error 521 (Web Server Down). Fix: Nginx/Apache is not listening on port 443 or host firewall (ufw/iptables) is blocking traffic.