GitHub Pages custom domain pogent.fun — TLS certificate still not provisioned after 19+ hours, DNS verified correct #213124
Replies: 5 comments
|
@jack777-max The docs list two things that can quietly block certificate issuance even when the DNS check passes: extra A, AAAA, ALIAS or ANAME records on the apex (or a CNAME on www/another subdomain you're not using with Pages), and CAA records that don't include letsencrypt.org. Since the Pages API shows no https_certificate at all, it's worth one more look at those. If you can paste the output of these, we can at least rule your side in or out: dig +short A pogent.fun If everything's clean, a staff member would have to look at the provisioning on their end. |
|
Thanks for the pointers — I just re-checked all of these via Google Public DNS:
So the DNS side looks fully ruled out: no extra apex records, and no CAA record that could block letsencrypt.org. It really seems the provisioning job is stuck on GitHub's side — staff help would be very welcome. Thank you! |
|
Hi, Your DNS records look correct for an apex domain, and 19 hours is still inside the window GitHub gives for certificate issuance, which is up to about 24 hours. Here is what I would check before treating it as a stuck job. 1. Check that both names resolve correctly For an apex domain, GitHub requests a certificate for dig pogent.fun A +short
dig www.pogent.fun CNAME +short
dig pogent.fun AAAA +short
dig www.pogent.fun AAAA +short
dig pogent.fun CAA +short
dig www.pogent.fun CAA +shortExpected: the four GitHub IPs for the apex, 2. Check DNSSEC A half-configured DNSSEC setup (a DS record at the registrar without matching signed zone data) can break validation even when ordinary lookups work. Check https://dnsviz.net/d/pogent.fun/dnssec/ . If DNSSEC is failing, fix it or disable it at the registrar. 3. Check the Pages settings and the repository
4. Verify the domain Under your account's Settings → Pages → Add a domain, verify 5. Try one more clean re-add, after waiting If you are past 24 hours with no change:
Repeating this many times can restart the process, so do it once. 6. If it still doesn't work Community members can't reset the provisioning job. Reply on your ticket (#5004754) and ask for human review, or open a new request at https://support.github.com/contact. Include:
Ask them to check whether certificate issuance is stalled for this domain. |
|
Since the DNS checks are already clean, one more thing worth checking is whether a fresh Pages deployment ran after you re-added the domain. Re-adding the domain on its own does not always start a new build, and the certificate step is tied to the deployment. Try pushing a small change, or an empty commit, so a new Pages build runs, then check the build log and the Pages API again after it finishes. It is also worth testing the www address separately from the apex address. If one of them loads over HTTPS and the other does not, that points to the certificate covering only one name. If neither works after a fresh deployment and more than 24 hours have passed, your support ticket is the right route, and the dig results and API output you already have are exactly what support needs to check the provisioning job. |
|
Hi! Since the Let's Encrypt TLS certificate provisioning job appears to be stuck in the queue, here are a few troubleshooting steps you can try: Verify CNAME Records: Ensure your DNS configuration correctly points your custom domain (pogent.fun) to your GitHub Pages user/organization site (jack777-max.github.io) without any conflicting records. Remove and Re-add (with a wait time): Try removing the custom domain from your repository settings, clearing the custom domain field entirely, saving it, and then re-adding it after a brief wait to trigger a fresh TLS provisioning cycle. Patience with Let's Encrypt Queues: Sometimes certificate generation queues can experience delays due to high traffic or rate limits. If the DNS and CNAME records are fully verified, it often resolves itself once the background queue processes the request. Since free accounts rely on community and self-service support options, hopefully, a staff member or community contributor can check the queue status for your specific domain soon. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
Hi everyone,
My GitHub Pages site for the repository jack777-max/pogent-site uses the custom domain pogent.fun, which was added on 2026-11-14 around 01:20 WIB (2026-11-13 18:20 UTC). More than 19 hours later the TLS certificate still has not been provisioned:
It looks like the Let's Encrypt provisioning job for this domain is stuck in the queue. Could a staff member please take a look and reset it? Any help is appreciated. Thank you!
All reactions