GitHub Pages: custom domain HTTPS certificate never issued (stuck at "new" / "authorization_created")

[douglas-mvca]

🏷️ Discussion Type

Bug

Body

Our GitHub Pages site (repo douglas-mvca/one-mitten-studio-website) has a custom domain, onemittenstudio.com, and GitHub has never issued an HTTPS certificate for it.

• Since about 2026-10-08, the certificate state stayed at authorization_created. We removed and re-added the custom domain twice (9 Oct), and nothing changed.
• On 13 Oct, we switched the custom domain to www.onemittenstudio.com. The state moved to new ("The certificate request process will begin shortly"), but it is still new more than 24 hours later.
• DNS: the apex has A records for 185.199.108–111.153, and www is a CNAME to douglas-mvca.github.io. There is no CAA record, and the DNS answers are the same on Google, Cloudflare and Quad9.
• GitHub's health check (/pages/health) reports both names as is_valid: true, is_https_eligible: true, caa_error: null and is_served_by_pages: true. The only error is https_error: peer_failed_verification.
• crt.sh shows no certificate ever issued for the domain, so the request never seems to reach Let's Encrypt.
• The site serves GitHub's *.github.io certificate. The site works over plain HTTP.

A support ticket (4850041) was closed because our account only has self-service support. Is there a way to restart the certificate request from GitHub's side, or is there something else we should check?

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