GitHub Community
GitHub Pages custom domain TLS certificate stuck at "Authorization created" #206854
Replies: 2 comments 1 reply
|
One thing worth testing before waiting any longer: the certificate covers both curl -sSI http://fenghuashen.com/.well-known/acme-challenge/test
curl -sSI http://www.fenghuashen.com/.well-known/acme-challenge/testYou want a plain Also worth ruling out: no proxy in front (a Cloudflare orange-cloud record would intercept the challenge), and no stray CAA record at the apex — you have already confirmed the CAA part. If both curls return 404 from Pages, there is genuinely nothing left on your side and it is queue-side. In that case this discussion cannot move it — support.github.com is the only route that can requeue provisioning. |
|
Thanks — I tested both endpoints as suggested. Both the apex and www hostnames return a plain HTTP/1.1 404 Not Found directly from Server: GitHub.com, with no 301/308 redirect: http://fenghuashen.com/.well-known/acme-challenge/test → 404 There is also no proxy in front of the site, and the earlier DNS checks confirmed no AAAA, CAA, or DS records. So this appears to further rule out a DNS or redirect issue on my side. The certificate state remains authorization_created, and HTTPS is still presenting the default *.github.io certificate. I’ll leave the DNS and Pages configuration unchanged for now. Thanks for helping narrow this down. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
I am seeing what appears to be another instance of the recent GitHub Pages custom-domain TLS provisioning issue.
Repository and domain
Repository:
jackyshenfenghua/fenghuashen.comCustom domain:
fenghuashen.comThe site is deployed successfully and works over HTTP, but GitHub Pages has not issued a TLS certificate for the custom domain.
Pages Settings remains at:
DNS Check in Progress1 of 3 — Certificate Requested: Authorization createdEnforce HTTPSis unavailableThe Pages API reports:
DNS and domain checks
I have verified the public DNS configuration:
fenghuashen.comresolves to all four current GitHub Pages IPv4 addresses:185.199.108.153185.199.109.153185.199.110.153185.199.111.153www.fenghuashen.comis a CNAME tojackyshenfenghua.github.iofenghuashen.comVerifiedHTTP requests to the apex domain return
200 OKfrom GitHub Pages, andwwwredirects to the apex domain over HTTP.HTTPS currently presents GitHub's default
*.github.iocertificate, which does not containfenghuashen.com, resulting in a hostname mismatch.Troubleshooting already performed
I have already:
Removing and re-adding restarted provisioning, but it became stuck again at
authorization_created.I also ran GitHub Support's "Troubleshoot Pages SSL issues" assistant, which confirmed that the domain is not currently presenting a valid SSL certificate.
Similar recent reports
Before posting, I searched the Community and found several recent reports describing very similar behavior, including domains stuck at
new,authorization_created, or continuing to receive the default*.github.iocertificate despite apparently valid DNS.In particular, discussion #206108 documents multiple affected domains and includes cases stuck at
authorization_created.My domain appears to be another independent data point with the same general provisioning symptom.
Question
Is there anything else that can be corrected on my side, or does
https_certificate.state: authorization_createdindicate that certificate provisioning is now waiting on GitHub Pages infrastructure?If someone from the Pages team is able to inspect the certificate provisioning state or queue for
fenghuashen.com, that would be greatly appreciated.For now I am leaving the DNS records and custom-domain configuration unchanged so that I do not restart the provisioning process again.
Thank you.
All reactions