Skip to content

05 · The Name-Collision Mystery

“i can’t login to the private / in the public i see docusaurus instead of astrogon”

Two bizarre symptoms. Both deployments were green. What could possibly serve Docusaurus from our Astrogon project?

Fact-gathering with curl:

  • public-docs.pages.dev/ → HTTP 200, but the HTML was the default Docusaurus template: canonical URL https://your-docusaurus-site.example.com/, “Docusaurus Tutorial - 5min ⏱️” button, facebook/docusaurus footer links.
  • public-docs-7mi.pages.dev/ (hash URL from the deploy log) → our real Astrogon build.
  • private-docs.pages.dev/ → HTTP 302 → ethpandaops.cloudflareaccess.com/cdn-cgi/access/login/private-docs.pages.dev — a foreign Cloudflare Access org. No way to log in.
  • private-docs-183.pages.dev/ → our real Starlight build, no gate at all.

The project list (user ran wrangler pages project list):

│ private-docs │ private-docs-183.pages.dev │ No │ 9 minutes ago │
│ public-docs │ public-docs-7mi.pages.dev │ No │ 9 minutes ago │

Root cause — the *.pages.dev namespace is global

Section titled “Root cause — the *.pages.dev namespace is global”

*.pages.dev hostnames are globally unique across every Cloudflare account in the world. The clean names public-docs.pages.dev and private-docs.pages.dev were already claimed by other accounts’ projects:

  • public-docs.pages.dev → someone’s throwaway Docusaurus template site
  • private-docs.pages.dev → someone’s project guarded by their Access app (org ethpandaops)

Our projects in our account only got the hash-suffixed domains (-7mi, -183). Every deploy succeeded, every URL behaved “differently” — there was never anything wrong with our builds. (Fun fact: the Docusaurus default theme also has an “Easy to Use” hero card — same title as what we first checked, which misled the first read of the site.)

The 302 pointed at a login page in an org we’d never seen, and the Docusaurus canonical was an example.com placeholder — both are textbook signs of templates deployed by someone else, not custom content. Once wrangler pages project list showed only hash domains, the collision theory was confirmed: the clean subdomains belong to other accounts, and Cloudflare gives the new project a random-suffix domain instead.


Renamed both pages projects to names nobody else would plausibly own:

Terminal window
public-docs → sambasene-public-docs
private-docs → sambasene-private-docs

Updated in the deploy workflows (pages project create / pages deploy --project-name), astro.config.mjs (site), wrangler.jsonc (name), and READMEs. Pushed → CI green → deploy green.

Verified live:

Terminal window
curl https://sambasene-public-docs.pages.dev/ # → 200, Astrogon ("Menu Open")
curl https://sambasene-private-docs.pages.dev/ # → 200, Starlight ("Welcome to Starlight | Private Docs")
  • The Docusaurus site and the ethpandaops gate were never ours — nothing to fix on their side
  • The impossible login was because the gate belonged to a different account; our actual private site had no gate (and still doesn’t — Access application still to be attached, see 06)
  • Long-term fix that makes collisions irrelevant forever: custom domain (e.g. docs.…dev) attached to the Pages project

While setting up Zero Trust, the user pasted Cloudflare WARP install instructions for Fedora. Two findings:

  1. WARP is not needed for Email-OTP Access — the identity provider does the gate, no client software required. WARP only matters for device-posture policies.
  2. The agent shell runs inside the Freedesktop SDK (Flatpak) runtime — rpm/dnf don’t exist there, so host package installation is impossible from the agent. System-level installs are always the user’s terminal.

Lesson: know your runtime. “Check the OS” returned a Flatpak sandbox, not Fedora — environment context beats assumptions.