[Bug] GitHub Pages SSL certificate stuck provisioning >48h (taropai.com)

[taropai1]

🏷️ Discussion Type

Bug

Body

Description

My GitHub Pages site with custom domain taropai.com has been stuck in "TLS certificate is being provisioned" status for over 48 hours, far exceeding the official 15–60 minute window. The Enforce HTTPS checkbox is grayed out, and HTTPS is completely unavailable.

What I've already verified & tried:

1. Removed and re-added the custom domain in Pages settings multiple times, waiting 15+ minutes each time for re-provisioning
2. Confirmed DNS A records are correctly set to GitHub Pages official IPs:
   • 185.199.108.153
   • 185.199.109.153
   • 185.199.110.153
   • 185.199.111.153
3. Disabled Cloudflare CDN proxy (all records set to DNS only) to eliminate certificate verification conflicts
4. Verified global DNS propagation via DNS Checker, with nearly all global nodes resolving correctly
5. Pages build is successful, HTTP access (http://taropai.com/) works normally, but HTTPS is down
6. The "Enforce HTTPS" checkbox remains grayed out due to the stuck certificate

Attached Screenshots:

1. Pages settings page showing certificate stuck status and DNS check success
2. Cloudflare DNS records page showing correct A records and proxy disabled
3. DNS Checker global propagation report showing successful resolution

Account & Repository Info:

• GitHub Username: taropai1
• Repository: taropai1/AI-Chef
• Custom Domain: taropai.com
• Issue Start Time: 2026-04-10 UTC+8 (stuck for over 48 hours as of submission)

Request

Please help manually trigger the TLS certificate provisioning or investigate the root cause of this stuck request.

Thank you!

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