`*.pages.dev` assignation bug
I've deleted a Pages project with an associated
*.pages.dev domain from one account and re-created the project on another account. This resulted in the same *.pages.dev being assigned (which seemed nice). But now the deployment on such domain does not work and further adding custom domains to it yields "CNAME Cross-User Banned" errors. Is this system eventually consistent and should I expect it to converge in few hours or is this just a bug?8 Replies
you added the custom domains in the pages project settings right? what status does it show for them?
@Erisa
-
{name}.pages.dev fails 522
- {hash}.{name}.pages.dev either 522 or unresponsive
- custom-domain is failing with error 1014 "CNAME Cross-User Banned"
Custom domain configuration is showing a generic "Domain is incorrectly configured". But the domain is correctly configured within the same account and the domain works correctly for other services. I've tried to remove and re-apply the custom domain, use a sub-domain and also use different domains from the same account (which works correctly for other Pages).
I would say I'm 90% positive it is cause the system thinks the {name}.pages.dev domain belongs to the old account.
I'm not comfortable sharing the exact details publicly, but if it can help I can provide them in DM.thanks @Borut Svara - if you happen to have a pro plan or higher then can you create a support ticket and share the ticket number? If youre on free thats not a problem just DM me the *.pages.dev domain and i'll escalate it
@Erisa is would assume Pro is different than the Paid Workers. Will DM thanks 😀
it is different yeah
Also just to make sure, you published a production deployment to the new project that shows as deployed successfully right?
Thanks for the DM, I escalated it to Cloudflare so someone will check when available
Yes, I just created a standard project via CLI and published a deployment (which is successful)
Thanks
Hey Borut! I'll DM you to get some more details on the specifics so we can look into this!