GitHub Pages TLS certificate stuck at 1 of 3 for 3 days despite valid DNS and HTTP 200

[ostepanovva]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Pages

Body

Hello GitHub Community,

My GitHub Pages TLS certificate provisioning has been stuck at step 1 of 3 for three days.

GitHub account: ostepanovva
Repository: https://github.com/ostepanovva/1c-google-reports
Custom domain: app.ostepanovva.ru

Current status:

• DNS Check in Progress
• TLS certificate provisioning: 1 of 3
• Message: "Certificate Requested: This domain was recently added. The certificate request process will begin shortly."
• Enforce HTTPS is unavailable

I have verified the following:

• CNAME: app.ostepanovva.ru → ostepanovva.github.io
• The record is returned correctly by both authoritative DNS servers: ns1.reg.ru and ns2.reg.ru
• Google DNS 8.8.8.8 returns the same CNAME
• There are no CAA records restricting Let's Encrypt
• HTTP request returns "HTTP/1.1 200 OK"
• The HTTP response contains "Server: GitHub.com"
• The Pages deployment is successful
• I already removed and re-added the custom domain to restart provisioning

The DNS configuration and HTTP routing appear to be correct, but the certificate remains stuck at step 1 of 3.

Could GitHub staff please inspect or reset the certificate provisioning state for this domain and repository?

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

[tayfuryldz]

Your DNS checks cover the usual causes pretty well. If the CNAME resolves correctly, Pages itself serves the domain, there is no restrictive CAA record, and removing/re-adding the domain still leaves certificate provisioning at 1/3 for days, there isn't much left to fix client-side.

I wouldn't keep removing and re-adding the domain now, because that can restart the provisioning flow and makes the timeline harder to diagnose. Keep the DNS stable and open a Support ticket with the repository, custom domain, the time it was last added, and the screenshot showing 1/3. Ask them to inspect/reset the Pages certificate provisioning state.

The HTTP 200 from GitHub is useful evidence here: routing is already reaching Pages, so this looks different from a basic DNS-to-Pages failure.

[ostepanovva]

Update: the issue is still unresolved. The TLS certificate provisioning remains stuck at step 1 of 3, and the DNS check is still in progress.

The DNS configuration has remained unchanged and continues to resolve correctly. The site is also accessible over HTTP with status 200 and is served by GitHub Pages.

Could a GitHub staff member please inspect or reset the certificate provisioning state for this domain?