Accidentally 301'd my entire domain
Hi all! I accidentally checked "all subdomains" on a bulk redirect from my apex domain to my
www domain, which was served via Cloudflare Pages. For a few days, it was serving a 301 redirect loop. I caught the issue and reverted the change. Now, when I visit the www domain, the site serves a 522 "Connection timed out" Cloudflare-branded status page. It's been about a day since I reverted the configuration. I can visit the website just fine by its foo.pages.dev domain. Does anyone know if there are other levers I can pull to get my site back, or have I permanently broken the entire domain?5 Replies
522 usually means the domain doesn't exist as a Custom Domain on the Pages project
Thanks @Erisa! I just checked the Pages configuration and it does indeed show that the custom domain is inactive. When I click Reactivate, it gives instructions to add the CNAME record to my DNS, which already exists. I've tried deleting and re-creating the CNAME, as well as turning off the Proxy switch in Cloudflare DNS
Ahh okay so the 301 loop probably led to the custom domain verification failing when it checked again - can you try deleting the Custom Domain entry and re-adding it?
It's weird that Reactivate didn't work but delete+readd should
Thank you! Delete + re-add was the fix I needed! Site is back up ✨
I'm new to this community, do I need to do anything special to mark this question as "answered"?
Right click the thread name, edit tags and then add "Solved"
