GitHub Pages custom domain stuck on default *.github.io certificate despite clean DNS and successful DNS check

[lebamath]

Discussion Type

Product Feedback

Discussion Content

Repo: lebamath/lebamath.github.io
Custom domain: www.wirelesssharenotes.com

I had a DNS misconfiguration (a domain registrar's "forwarding" feature had injected two extra A records alongside the correct GitHub Pages A records: 185.199.108.153 / .109 / .110 / .111). This caused an invalid HTTPS certificate — the site was serving the default *.github.io wildcard cert instead of a domain-specific one.
I fixed the DNS a few days ago. It's now clean:

• Only the 4 official GitHub Pages A records + 4 AAAA records remain (verified via 8.8.8.8, 1.1.1.1, and the domain's own authoritative nameserver)
• No CAA records exist, so certificate authority authorization isn't the blocker
• CNAME file content served by the site is exactly "www.wirelesssharenotes.com", no stray whitespace/newlines
• Settings → Pages shows "DNS check successful"
  But "Enforce HTTPS" is still unavailable with: "Unavailable for your site because your domain is not properly configured to support HTTPS". Connecting directly to the GitHub Pages IPs with SNI www.wirelesssharenotes.com still returns CN=*.github.io, not a cert for my domain.
  I've tried Remove → wait → re-add → Save multiple times over the past couple of days with no change. It's been well over 24 hours since DNS became clean (GitHub's own docs say up to an hour, sometimes needing the remove/re-add nudge).
  Has anyone run into a certificate provisioning that stays stuck like this even after DNS is fixed? Is there something else that can get it unstuck, or does it just need more time / a GitHub-side manual retrigger?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[initial-d]

I checked it from outside as well, and your current state looks past the normal DNS-misconfiguration phase.

What I see now:

www.wirelesssharenotes.com CNAME -> wirelesssharenotes.com.
wirelesssharenotes.com A -> 185.199.108.153 / .109 / .110 / .111
wirelesssharenotes.com AAAA -> 2606:50c0:8000::153 / ::8001::153 / ::8002::153 / ::8003::153
CAA -> no restrictive CAA record returned

HTTP is already reaching GitHub Pages:

HTTP/1.1 200 OK
Server: GitHub.com
X-GitHub-Request-Id: AB90:37E476:129D45:150042:6A90CA3D

But HTTPS still fails on hostname validation:

SSL: no alternative certificate subject name matches target host name 'www.wirelesssharenotes.com'

GitHub's Pages HTTPS docs describe the normal sequence as: DNS check succeeds, GitHub queues a Let's Encrypt certificate request, then uploads the certificate to the Pages TLS termination layer:
https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https

Given that your Pages UI says the DNS check is successful and an external HTTP request is already served by GitHub Pages, I would stop removing/re-adding the domain repeatedly. At this point repeated churn can make the timeline harder to debug without adding much new signal.

The support/community packet I would keep updated is:

1. Repository: lebamath/lebamath.github.io
2. Custom domain: www.wirelesssharenotes.com
3. Time when DNS became clean, in UTC if possible
4. Pages UI status: DNS check successful, HTTPS unavailable
5. External evidence: HTTP 200 from Server: GitHub.com, but SNI HTTPS still serves a certificate without www.wirelesssharenotes.com
6. Confirmation that there are no extra A records, no restrictive CAA records, and the CNAME file exactly matches the custom domain

If it stays in this state well beyond the documented provisioning window, the remaining fix probably has to be on GitHub's side: requeue or repair the Pages certificate issuance/binding for that hostname.