Pages HTTPS certificate stuck in "new" for ~3 weeks (apex caviar.group), DNS verified correct

[aslankaa1-droid]

🏷️ Discussion Type

Bug

Body

My GitHub Pages custom-domain certificate has been stuck and never gets issued.

• Repository: aslankaa1-droid/caviar
• Custom domain (apex): caviar.group
• Pages status: built
• https_certificate.state: "new" — stuck since ~2026-06-10, about three weeks.
• https_enforced: false (can't enable — no valid certificate).

The site is reachable over HTTP (200), but HTTPS serves a certificate that does not match the hostname:
curl → schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL.

I verified every documented requirement:

• Apex A records: 185.199.108.153 / .109 / .110 / .111.
• No AAAA on the apex. No CAA. No wildcard (*.caviar.group).
• www.caviar.group is a CNAME to aslankaa1-droid.github.io.
• CNAME file in the repo root contains exactly: caviar.group
• Certificate request domain shows only caviar.group.
• Already did a clean reset (removed/re-added custom domain) and waited several weeks.
• HTTP-01 challenge path returns 200 over HTTP.

Everything on the DNS/repo side matches requirements, yet the certificate never leaves "new". This looks like a backend provisioning issue. Could a staff member please re-trigger / investigate the Let's Encrypt provisioning for caviar.group? Thank you.

(Support ticket #4519773 was closed as out-of-scope for the free plan and redirected here.)

[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. ⭐