Pages API keeps https_certificate.state at authorization_created after the certificate is issued and served (sigetar.ru)

[Sagargupta16]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Pages

Body

Repository observed: https://githubfast.kdns.fr/SigetarWorld/eve-pi-planner (public, custom domain sigetar.ru, reported stuck in #209602). I am not the owner; everything below is from an unauthenticated GET and a TLS handshake.

What I expected

Once Pages has issued the certificate for a custom domain and the edge serves it, GET /repos/{owner}/{repo}/pages should report https_certificate.state: approved with an expires_at, the way it does for other sites (k4hvecii/k4hvecii.github.io shows approved, expires_at 2026-12-31).

What happens

The edge serves a real certificate, but the API still reports the first ACME step. Checked 2026-10-10 01:45 UTC and again 03:10 UTC, same result both times:

openssl s_client -servername sigetar.ru -connect sigetar.ru:443
  subject   CN=sigetar.ru      SAN: sigetar.ru
  issuer    Let's Encrypt YE1
  notBefore 2026-10-09 02:37:00 UTC   notAfter 2027-01-07 02:36:59 UTC

GET /repos/SigetarWorld/eve-pi-planner/pages
  status                 built
  build_type             legacy
  cname                  sigetar.ru
  protected_domain_state verified
  https_enforced         false
  https_certificate      { state: authorization_created,
                           description: "Authorization created",
                           domains: [sigetar.ru] }      (no expires_at)

So for at least 24 hours the API has said "Authorization created" for a certificate that was issued and deployed on 2026-10-09 02:37 UTC.

Why it matters

This field is the only issuance progress users can read; pages/health has no certificate status. Owners in #209602, #209794 and #209943 are deciding whether to remove and re-add their domain based on it, and a re-add restarts issuance. A stale authorization_created makes people restart something that already finished. If the Enforce HTTPS gate reads the same field, the owner also cannot turn HTTPS on: #209602's author got "The certificate has not finished being issued" from PUT /pages with https_enforced=true while the state was authorization_created.

Ask

Reconcile https_certificate.state with actual issuance (or document that the field can lag by a day or more), and confirm whether https_enforced can be enabled while the field is stale. Happy to re-check any time; the domain and timestamps above are enough to reproduce from your side.

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