Cloudflare Pages can't associate with a domain

[gareth3]

Hi,

We’re moving away from Azure CDN to pages - so far everything’s been wayy better.

One issue though:

Got a Cloudflare Pages site up and running - all works fine on the pages.dev domain: https://timetastic.pages.dev/

Tried to associate our apex domain to it and it’s stuck on verifying:

Been like this for a week now.

We use Cloudflare everywhere on this domain, nameservers, load balancers (on a subdomain), the lot.

Tried it with another domain we have and it all works fine (timetastic.us) , so I think there must be something up with the .co.uk - any tips?

The docs say if I try to do the DNS manually it won’t work - it has to be done through Pages.

Any help appreciated,

Thanks

Gareth

[matteo]

Seems a very easy thing to try, but… have you tried deleting it and recreating the domain association?

[gareth3]

I’ll admit I hadn’t - the big scary warnings put me off

Just tried now, I’ll see if it updates.

[gareth3]

What’s my next step after that?

I’d expect verification to be quite quick as Cloudflare handle our DNS. Global propagation of the record could take 48hours but Cloudflare can confirm before then, right?

Just get the feeling this isn’t fixed yet!

Tested it out with another domain (got a few spare!) and it validated instantly:

So I think something’s up with the .co.uk here - any ideas how I can debug this?

I bet it’s because Azure still have a certificate set up for the .co.uk apex domain for their CDN, even though it’s expired:

[Walshy]

Hey,

Looks like we’re unable to validate the hostname because of a redirect:

$ curl -I https://timetastic.co.uk/.well-known/acme-challenge/randomstring

HTTP/2 301
date: Mon, 01 Aug 2022 12:09:42 GMT
location: https://timetasticletsencrypt.blob.core.windows.net/letsencrypt-siteextension/.well-known/acme-challenge/randomstring

[gareth3]

Hi,

Thanks for the deply.

ah this is the letsencrypt site extension we use for the subdomain SSL validation on the app subdomain. I’ve changed the page rule to only act on subdomains so the apex should validate now.

I’ll probably have to add a special case for the www redirect too

Am I best deleting and retrying or just waiting for it?

[Walshy]

Looks like it is now valid on my end

[gareth3]

ahh yes, you beautiful humans!

Thanks everyone, appreciate your swift responses. Such a nice experience compared to Azure lately!