Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cloudflare: moving a site's zone to another Cloudflare account without downtime

Open Beginner friendly
  • Is something wrong?
#210 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
devops, documentation

Research direction

Start with content/6.deployment/6.cloudflare.md and read the existing purge callout to match its style. Add a short section covering the account move sequence, TLS transition, cross-account CNAME limitation, purge configuration, and shared rate limit from the issue. Done when the guidance includes these steps and matches the site's documentation conventions.

Written by the indexing model from the issue text.

Description

Found while moving the six smoking/alcohol zones from one Cloudflare account to their own (2026-10-11). content/6.deployment/6.cloudflare.md doesn't cover moving a zone between accounts. Worth a short section:

  • No API move for a zone. A move means creating the zone in the new account (Pending), copying DNS records, settings and rules (rate limit, cache rules, bot settings), then changing nameservers at the registrar. Settings and rules aren't carried over automatically.
  • No TLS gap at activation. On Free, a full-setup zone gets its Universal SSL certificate only after it activates (15 min to 24 h), and it can't be pre-validated. So set every proxied record DNS only in the new zone before switching: the template's ingress already serves a valid Let's Encrypt certificate on each hostname. Switch the records back to Proxied once the zone's edge certificate is active. Edge caching only starts then.
  • A proxied CNAME to a hostname in another account's zone fails with error 1014 (CNAME Cross-User Banned). A media hostname such as cdn.<site> pointing at a shared cdn. hostname in another account must point at the origin directly (e.g. an A record to the bucket's load balancer), as long as that origin has a certificate for the name.
  • Purges: set CADDY_CACHE_CDN_CONFIG with the new zone ID and deploy before the zone goes live. A tag purge to a zone that's still Pending returns 403 Unable to purge, logged by Souin and harmless.
  • Several sites on one account share Free's 5 purges a minute. Six sites used CWA_API_CLOUDFLARE_PURGE_REQUESTS=1, _WINDOW=90s, _BURST=3 each (the existing callout's example covers two sites at REQUESTS=2; a window longer than 1m is how to go below one a minute).
Dominant language
Vue
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.