DNS check Successful - Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS, even after a long time

[Liternal]

I have been using a custom domain, connorkellygamedev.com, from namecheap and have been trying to get it set up, but it has not been allowing me to enforce HTTPS, and I do not know why. Here are my host records on namecheap, and I have checked them over and over and it seems this is what it is supposed to be.

A Record | @ | 185.199.108.153 | 30 min
A Record | @ | 185.199.109.153 | 30 min
A Record | @ | 185.199.110.153 | 30 min
A Record | @ | 185.199.111.153 | 30 min
CNAME Record | www | Liternal.github.io.

I have both been told I need to buy an SSL certificate, and told I don't need one.
Here is one of the guides I used: https://gist.github.com/plembo/84f80c920bb5ac6f19e53fe6f8db1ff7
I have also looked at the official documentation (https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages#https-errors and https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https) and they have not been helpful.
If there is anything I can do to help, please let me know.

[mecodeatlas]

Hey @Liternal! Thanks for sharing all the details — it looks like you’ve done most of the setup correctly.

This message (“Unavailable for your site because your domain is not properly configured to support HTTPS…”) can sometimes show up even when the DNS records seem fine, usually because:

• DNS propagation is still in progress (even if it's been a couple of days).
• The CNAME file in your repo might be missing or misconfigured.
• There’s a redirect, proxy, or service (like Cloudflare) interfering with HTTPS.
• Or, less commonly, GitHub Pages might just be taking a bit longer to provision the SSL cert.

A few things you could double-check:

• Make sure your CNAME file exists in the root of your publishing branch and contains only: Liternal.github.io
• Try toggling the custom domain off and back on in the repository settings.
• Clear any conflicting DNS entries (like AAAA records or old CNAMEs).
• If you're using any DNS-level services (e.g. Cloudflare), check that they're not forcing redirects or SSL policies that conflict with GitHub's.

If everything looks good and it still doesn’t work after 24–48 hours, it might be worth opening a ticket with GitHub Support so they can take a closer look.

Hope this helps!

[Liternal]

Hi, I checked my CNAME file, and while it exists in the root of the branch, it contained connorkellygamedev.com rather than Liternal.github.io. I changed that to it and pushed it, but later it got changed back to connorkellygamedev.com without me doing anything, in an update I had to pull. Is that anything to worry about?

I do not think it is a problem with having to wait, since I have been waiting for DNS to propagate for around a week before asking here.

[Liternal]

Namecheap had another listed A record that I could not find on the site, after contacting support I got it removed and now my site is enforced by https.