Part of the custom domain process is issuing a certificate for that hostname, which respects the CAA
Part of the custom domain process is issuing a certificate for that hostname, which respects the CAA records on your root domain.
KKBy default, Cloudflare uses these ones.
KAdd in the ones that you're missing - in this case,
issue "digicert.com", issuewild "digicert.com" and issuewild "letsencrypt.org" then give it another go.
IGitLab?
IYeah... there's a known bug there. There's a solution though.
IGo into your Webhooks and delete one of the Cloudflare ones (you'll see two)
I(It's being looked into by the team)
IEither one 
IIt's just because when you added the project it got duplicated somehow, but both work and you can delete either one.
IThe team's working on a fix
INo problem 
IYeah, its not.
IAll commits get deployed once. If they're on the Production branch they will get put on both your pages.dev and your custom domain, if they're on any Preview branch only the pages.dev (with a prefix)
WGo for it
WCorrect
Wyep, we add a CORS header for you
W(which you can change or remove if you want)
K
ICan you try going to your pages.dev domain with a path of
/cdn-cgi/traceIf it won't load anything then it's a problem with your VPN's connectivity to the Cloudflare network.
IThen your site should load... what kind of site is it? Is there anything you're doing to make it not work?
I(for example, turning on an adblocker, blocking VPN connections, that kind of thing)
