GitHub Pages: custom domain certificate stuck at "Certificate Request Error" for ultraomeaga.loc.cc #213482
Replies: 1 comment
|
I run GitHub Pages sites with custom domains, and the one part of your setup I'd change is the flattened CNAME at the apex, Your DNS resolves, and GitHub's check passes it - but the certificate pipeline is pickier than the DNS check, and CNAME flattening is the one piece here that isn't GitHub's documented apex configuration. What I'd try, in this order:
A: 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153 AAAA: 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153
After the re-add, give it a full hour before judging - the "1 of 3" step should move once Let's Encrypt can validate against a textbook apex setup. If it's still throwing Certificate Request Error 24 hours after the A-record change, then it really is a stuck job on GitHub's side and there's nothing left on yours - at that point, posting your dig output and this timeline in the thread is the best escalation a free plan has, since staff do read this category. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
Hi all,
My GitHub Pages custom domain certificate has been stuck for over 15 hours across two separate provisioning jobs, and I am hoping someone from the GitHub team or the community can help unstick it.
Setup
mohwyyyss/ultraomeaga(public, Pages enabled, Deploy from branch, main, / root)ultraomeaga.loc.cc(CNAME file in the repo contains exactly this)mohwyyyss.github.io(flattened by my DNS provider), resolving to GitHub's Pages IPs (185.199.108–111.153 and the IPv6 equivalents)What I see in Pages settings
*.github.iocertificate (NET::ERR_CERT_COMMON_NAME_INVALID)Timeline
What I have already ruled out
loc.cc, or atccloc.ccis on the Public Suffix List, so this domain has its own limit budget, and zero certificates have ever been issued for itwwwsubdomain is intentionally not configuredEverything externally checkable looks correct, so the failure appears to be inside GitHub's certificate provisioning pipeline for this domain. Is there anything else I can do from my side, or can someone from the GitHub team take a look at the stuck provisioning job?
Thanks in advance!
All reactions