What this error means
Error 522: Origin server timeout — Cloudflare cannot establish connection to origin is a Cloudflare failure pattern reported for developers trying to diagnose and fix 522 timeout errors affecting cloudflare-backed sites, especially workers applications and proxied dns zones. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Error 522 is one of Cloudflare's most commonly searched errors. Affects paying Cloudflare Pro/Business customers whose sites go down unexpectedly. Many root causes (firewall rules, WAF blocks, origin overload) make troubleshooting complex and searchable. Covered-errors has basic entry but no Workers-specific variant.
Common causes
- Error 522 is one of Cloudflare's most commonly searched errors. Affects paying Cloudflare Pro/Business customers whose sites go down unexpectedly. Many root causes (firewall rules, WAF blocks, origin overload) make troubleshooting complex and searchable. Covered-errors has basic entry but no Workers-specific variant.
Quick fixes
- Confirm the exact error signature matches
Error 522: Origin server timeout — Cloudflare cannot establish connection to origin. - Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.