I switched my custom domain to the “www” subdomain but I had tried that before (unsuccessfully) so when it finally worked I had the impression that the issue was fixed on GitHub’s side.

OK I actually figured out a fix, I’m using Cloudflare as my domain registrar, and in my DNS settings, my 4 A records that point to Github had the “proxied” type on them, and appreantly GitHub doesn’t like that, so I switched from “proxied” to “DNS only” (by just clicking on the word ‘proxied’), and it seems to work with my custom domain (without the www subdomain). and now the certificate is issued and things are looking good, I hope this helps someone out!

I was having a similar issue. Waiting for 24h hours didn’t fix anything. It turns out the problem was that my domain was parked by default (my domain provider is GoDaddy). I removed the parking A record, and 5 minutes later the TLS certificate was obtained. Then I could finally enable the “Enforce https” option in the GitHub pages settings. Then another 5 minutes later, my GitHub pages were online.

TLDR: try to remove the " A @ Parked" record in your domain provider DNS settings and then enable “enforce https” in GitHub pages settings.

I managed to solve it as most of you mentioned, unchecking the proxy option in the dns zone for the main domain (in my case cloudflare). However, there are some considerations to make:

If you have been using features like cache and workers, which need the server to process your request before actually accessing the website that is hosted on github, you will have problems with the functioning of your website when removing proxied.

In my case, using cloudflare I did the following:

• I removed the A entries of the proxied github from the dns zone in the cloudflare;
• I connected the enforce https via github pages;
• I waited for github pages to renew my tls certificate;
• I reconnected to A entries to be proxied again (on cloudflare);

I have to do this every 3 months, as github doesn’t seem to renew the certificate automatically, for cloudflare to automatically recognize the new certificate.

Yeah it’s working you all have do to first delete all DNS record and these 5records only then you domain is ready for hosting through GitHub.

I also had the same problem just now, and it turns out the issue was in using a national alphabet domain.
In "custom domain" field in Github, I changed матяш.рф domain name to punycode xn--80axty8a.xn--p1ai and the TLS certificate was issued within a couple of minutes.

In my case, after waiting for about 22 hours and no certificate being issued, I simply deleted my subdomain.domain.com in GitHub Pages control panel and replaced with the same subdomain.domain.com. I waited for a minute and the certificate was up and running. I think GitHub tries to do the verification too early and it fails. For some reason, it don't retry the verification process unless you input a domain name again.

Just FYI,

if you enable proxy on Cloudflare to GitHub pages, GitHub cannot generate the certificate.
So, I need to disable the proxy (only use DNS service on Cloudflare) deleted my subdomain.domain.com in the GitHub Pages control panel, and replaced it with the same subdomain.domain.com.

@otter-computer Certificate Request Error: Certificate provisioning will retry automatically in a short period, please be patient.
I receive this error every single time the TLS certificate tries to be provisioned. It’s been over 24 hours.
Should I be panicking, or is this normal?
My website link is kidkalc.com

I am facing the same issue.

As mentioned in GitHub Docs and several replies, I have 4 A records and 1 CNAME record. There is no proxy setting equivalent on my registrar. I tried removing the verified domain and re-adding it. The DNS lookup is successful but it cannot generate a TLS certificate. What am I missing here?

CPANEL

DIG