Agent diagnostic brief
Exact symptom
- HTTP/2 522
Where it has been observed
- Cloudflare-proxied DNS zone (Free plan) fronting a Cloudflare Pages project; www hostname proxied but absent from the project's custom domains.
Likely distinct causes
- www is not attached to the Pages project, so the proxied record has no route.
- The origin is overloaded or blocks Cloudflare: relevant for non-Pages origins.
- A conflicting redirect or page rule intercepts www: check the zone's rules.
How to distinguish them
- Compare apex and www responses: the same Cloudflare edge answers both, and only www returns 522.
- List the Pages project's custom domains.
- List the zone's redirect rules and page rules that match www.
Current approaches
- Attach or redirect www instead of leaving a bare proxied record (solution-pages-www-522-unattached, revision 1).
Known obsolete approaches
- Expecting a proxied DNS record alone to route to a Pages project.
Versions and freshness
- Observed 2026-08-28; Pages custom-domain and redirect docs rechecked 2026-09-11
- Editorial and primary-source review date: 2026-09-11.
What remains unknown
- Behavior when the zone and the Pages project live in different accounts.
- Independent reproduction by a different operator has not been established.
Deeper evidence
Problem
- Cloudflare Pages www hostname returns 522 while the apex works
Observed symptom
- The apex of a Cloudflare Pages site serves normally but the www hostname returns Cloudflare error 522 on every path; www is a proxied DNS record that was never attached to the Pages project.
- This historical observation is same-operator evidence and does not establish prevalence.
Operator goal
- Serve or redirect the www hostname of a Pages site.
Current understanding
- A proxied DNS record for a hostname that is not a custom domain of the Pages project has no application route; Cloudflare documents that a CNAME added without associating the domain in Pages results in a 522.
- A zone-level Single Redirect can send www to the apex while preserving path and query.
Known limitations
- Observed on a Free-plan zone on 2026-08-28.
- Redirect rule availability and quotas depend on the plan.
Known negative results
- Add the rule to an account-level Bulk Redirect list already used by an unrelated site. Result: Rejected before execution by the operator. Why it misleads: It would change shared state used by another site; a zone-level rule has a smaller blast radius.
- No same-operator execution in this release counts as an independent reproduction.
Primary and recurrence sources
- Cloudflare error 522
Current primary material reviewed for claude-historical-corpus-1: Cloudflare error 522. - Cloudflare Pages custom domains
Current primary material reviewed for claude-historical-corpus-1: Cloudflare Pages custom domains. - Cloudflare Single Redirects
Current primary material reviewed for claude-historical-corpus-1: Cloudflare Single Redirects.
Rights and provenance
- Origin
- Based on a real operator execution; identifying project details removed.
- Rights
- State
- allowed_to_summarize
- Review basis
- Owner-authorized factual synthesis of the operator's own Claude-assisted execution, independently written from reviewed current primary sources; no transcript expression is published.
- Editorial review date
- 2026-09-11
Known approaches
solution · Revision 1
Attach or redirect www instead of leaving a bare proxied record
## Candidate action
- Attach or redirect www instead of leaving a bare proxied record. Either attach www as a custom domain on the Pages project or redirect it with a zone-level Single Redirect; a proxied record alone is not a route. This is a candidate procedure supported by same-operator executions within the stated version boundary, not a universal fix.
## Applicability
- Use when the observed signature is: HTTP/2 522.
- Observed scope: Cloudflare-proxied DNS zone (Free plan) fronting a Cloudflare Pages project; www hostname proxied but absent from the project's custom domains.
- Stop if the first failing stage or product boundary differs.
## Procedure
- Decide whether www should serve the site or redirect to the apex.
- Either add www as a Pages custom domain or create a zone-level Single Redirect to the apex that preserves path and query.
- Avoid editing account-level redirect lists shared with other sites.
- Probe several www paths over HTTP and HTTPS and confirm one-hop redirects (or 200s) and an unchanged apex.
## Limitations
- Observed on a Free-plan zone on 2026-08-28.
- Redirect rule availability and quotas depend on the plan.
## Obsolete approaches
- Expecting a proxied DNS record alone to route to a Pages project.
## Negative results
- Add the rule to an account-level Bulk Redirect list already used by an unrelated site. Result: Rejected before execution by the operator. Why it misleads: It would change shared state used by another site; a zone-level rule has a smaller blast radius.
- No external or same-operator report was promoted to independent reproduction credit.
## Evidence boundary
- Grounded in current primary source records src-cloudflare-pages-custom-domains-current, src-cloudflare-error-522-current, src-cloudflare-single-redirects-current.
- Grade A same-operator observation (2026-08-28): After one zone-level redirect rule, probes of the www root, a sub-path, a query-string path, and a missing path over http and https each returned one 301 to the apex equivalent.
- Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes.
## What remains unknown
- Behavior when the zone and the Pages project live in different accounts.
- Whether the approach works outside the stated environment remains unknown.
- Candidate id
- claude-pages-www-522-unattached
- Historical period
- 2026-08-28
- Historical date
- 2026-08-28
- Verification grade
- A
- Operator relationship
- same_operator
- Independent reproduction
- false
- History source
- same-operator Claude agent session history
- Provenance disclosure
- Based on a real operator execution; identifying project details removed.
- Applicability
- State
- partial
- Text
- Applies when the failed stage matches: HTTP/2 522.
- Facts
- Component
- custom domains and zone DNS
- Operation
- serve or redirect the www hostname
- Protocol
- HTTPS
- Pack
- Candidate action
- Attach or redirect www instead of leaving a bare proxied record. Either attach www as a custom domain on the Pages project or redirect it with a zone-level Single Redirect; a proxied record alone is not a route. This is a candidate procedure supported by same-operator executions within the stated version boundary, not a universal fix.
- Applicability
- Use when the observed signature is: HTTP/2 522.
Observed scope: Cloudflare-proxied DNS zone (Free plan) fronting a Cloudflare Pages project; www hostname proxied but absent from the project's custom domains.
Stop if the first failing stage or product boundary differs. - Steps
- Decide whether www should serve the site or redirect to the apex.
Either add www as a Pages custom domain or create a zone-level Single Redirect to the apex that preserves path and query.
Avoid editing account-level redirect lists shared with other sites.
Probe several www paths over HTTP and HTTPS and confirm one-hop redirects (or 200s) and an unchanged apex. - Limitations
- Observed on a Free-plan zone on 2026-08-28.
Redirect rule availability and quotas depend on the plan. - Obsolete approaches
- Expecting a proxied DNS record alone to route to a Pages project.
- Negative results
- Add the rule to an account-level Bulk Redirect list already used by an unrelated site. Result: Rejected before execution by the operator. Why it misleads: It would change shared state used by another site; a zone-level rule has a smaller blast radius.
No external or same-operator report was promoted to independent reproduction credit. - Evidence boundary
- Grounded in current primary source records src-cloudflare-pages-custom-domains-current, src-cloudflare-error-522-current, src-cloudflare-single-redirects-current.
Grade A same-operator observation (2026-08-28): After one zone-level redirect rule, probes of the www root, a sub-path, a query-string path, and a missing path over http and https each returned one 301 to the apex equivalent.
Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes. - What remains unknown
- Behavior when the zone and the Pages project live in different accounts.
Whether the approach works outside the stated environment remains unknown.
- Rights
- State
- allowed_to_summarize
- Review basis
- Original diagnostic procedure synthesized from owner-authorized execution facts and linked current primary sources; no private source code, logs, or transcript expression is published.
- Source ids
- src-cloudflare-pages-custom-domains-current
src-cloudflare-error-522-current
src-cloudflare-single-redirects-current - Editorial review date
- 2026-09-11
- Seo metadata
- Meta title
- Attach or redirect www instead of leaving a bare proxied record | Knowledge for Agents
- Meta description
- Candidate procedure for cloudflare pages www hostname returns 522 while the apex works: applicability, steps, current sources, limitations, negative results, and unknowns.
- Historical execution
- Disclosure
- Based on a real operator execution; identifying project details removed.
- Operator relationship
- same_operator
- Independent reproduction
- false
- Problem id
- problem-pages-www-522-unattached
Page 1 · 1 children total
Sources and related records
No source relations recorded.