Pages custom domain certificate permanently stuck at authorization_created

[SigetarWorld]

🏷️ Discussion Type

Bug

Body

Repository / site

• Repository: SigetarWorld/eve-pi-planner
• Pages URL: https://sigetarworld.github.io/eve-pi-planner/
• Custom domain: sigetar.ru
• Build type: legacy, source branch main, path /

The site is live and healthy over HTTP the entire time. There has been no outage.

Domain verification is fine

Domain verification succeeded. The _github-pages-challenge-SigetarWorld TXT record is present and publicly resolvable from multiple resolvers, and GitHub reports protected_domain_state: verified.

$ dig +short TXT _github-pages-challenge-SigetarWorld.sigetar.ru @1.1.1.1
"d962703d2e88aa9af41bd9cd52df44"

The problem

The Pages configuration is stuck:

"https_certificate": {
  "state": "authorization_created",
  "description": "Authorization created",
  "domains": ["sigetar.ru"]
},
"protected_domain_state": "verified",
"https_enforced": false

Enabling HTTPS returns:

$ gh api --method PUT repos/SigetarWorld/eve-pi-planner/pages -F https_enforced=true
gh: The certificate has not finished being issued (HTTP 404)

The state never advances. Authorization created is the first of the three ACME steps, and after five days across two separate attempts it is still there.

Two independent authorizations, same result

1. First authorization: created after domain verification on Oct 1. Stuck for ~17 hours.
2. Second authorization: I detached the custom domain (removed the CNAME file, waited for GitHub to release the domain, ~20s) and reattached it, which produced a fresh authorization. That one is also stuck at authorization_created, now for ~4 days.

A fresh Pages build (POST /pages/builds) made no difference in either case.

No certificate exists anywhere

No certificate for sigetar.ru appears in public Certificate Transparency logs. Both crt.sh and Cert Spotter return zero issuances for the domain and all subdomains, so no CA has issued anything.

Everything on the DNS side checks out

$ dig +short SOA sigetar.ru @ns3-l2.nic.ru
ns3-l2.nic.ru. dns.nic.ru. 2026093008 1440 3600 2592000 600

$ dig +short A sigetar.ru
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

• SOA serial 2026093008 is identical on all five authoritative nameservers (ns3-l2, ns4-l2, ns8-l2, ns4-cloud, ns8-cloud), so the zone is fully propagated.
• No CAA record at the apex, so issuance is not restricted by policy.
• Port 80 is served by GitHub (Server: GitHub.com), so an HTTP-01 challenge is reachable.
• No _acme-challenge TXT record exists, consistent with HTTP-01 validation.
• githubstatus.com reports Pages operational, with no open incidents.

Question

Is there something on the GitHub side that would keep the ACME authorization in authorization_created indefinitely? And is there a way to have the provisioning job re-triggered, short of detaching and reattaching the domain?

Thanks in advance.

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

[reddy895]

This looks like a GitHub Pages-side ACME provisioning issue rather than a DNS problem. Since domain verification, DNS propagation, HTTP reachability, and two separate authorization attempts all check out, the persistent authorization_created state suggests the certificate provisioning job may be stuck. GitHub staff may need to re-trigger or reset the certificate issuance process.