GitHub Pages TLS certificate stuck at "Certificate Requested" (step 1 of 3) for 17+ hours

[papakult]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Pages

Body

My GitHub Pages site papakult/b2china-site uses the custom domain b2china.ru. The HTTPS certificate is not being issued.

Current status in Settings > Pages

• "DNS Check in Progress"
• "TLS certificate is being provisioned", step 1 of 3, "Certificate Requested"
• Enforce HTTPS is unavailable
• The site is served with the default *.github.io certificate

What I have already tried

• Removed the custom domain and added it again (Sep 25, about 12:50 UTC). Provisioning started but never moved past step 1.
• Added the account-level verified domain TXT record _github-pages-challenge-papakult.b2china.ru. It resolves publicly, but the domain still shows as unverified after clicking Verify.

DNS (checked via 8.8.8.8, nameservers ns1.reg.ru / ns2.reg.ru)

• b2china.ru A: 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153
• www.b2china.ru CNAME: papakult.github.io
• No AAAA, no CAA records
• CNAME file in the repo root contains b2china.ru, publishing from main / root, builds succeed

I have another domain on GitHub Pages with the same DNS setup that got its certificate fine. Is there anything else I can do on my side, or can someone from GitHub re-trigger the certificate job for b2china.ru?

Thank you!

[TeWei02]

Your DNS itself looks right (four A records on the apex, www CNAME to papakult.github.io, no CAA in the way). The line that stands out is this one:

Added the account-level verified domain TXT record ... but the domain still shows as unverified after clicking Verify.

Certificate issuance does not start while a custom domain is unverified, so "Certificate Requested" parked at step 1 is consistent with the verification step never having completed rather than with the certificate job being stuck.

Check what is actually published â�� for b2china.ru the host field at the DNS provider should hold the short name _github-pages-challenge-papakult, with the zone appended for you:

dig +short TXT _github-pages-challenge-papakult.b2china.ru @8.8.8.8

If that is empty, look for a doubled zone:

dig +short TXT _github-pages-challenge-papakult.b2china.ru.b2china.ru @8.8.8.8

While in the zone, also confirm there is nothing that can silently block issuance:

dig +short CAA b2china.ru @8.8.8.8
dig +short A b2china.ru @8.8.8.8

An empty CAA answer is fine. A CAA that lists only a CA other than letsencrypt.org is not: it blocks the challenge without any visible error on the Pages page.

Then, in order:

1. Fix the TXT name if it was published under the doubled name, click Verify, and wait until the domain is reported as verified.
2. Remove the custom domain and add it back so the DNS check re-runs from scratch. Pushing a change to the CNAME file forces a Pages rebuild, but it does not re-queue certificate issuance on its own.
3. If the domain shows verified and the certificate is still at step 1 after a few hours, only GitHub Support can re-trigger that job â�� there is no API or setting for it. Include the DNS output above and note that Enforce HTTPS never became selectable.

One extra thing to rule out with reg.ru: some plans keep a parking/redirect service in front of the domain. If an HTTP request to b2china.ru is answered by the registrar rather than by GitHub, the HTTP-01 challenge for the certificate never reaches the Pages servers.

[almo2934-max]

Hello GitHub Community,

I am experiencing a GitHub Pages custom-domain TLS provisioning issue that appears to be stuck.

Repository:
https://github.com/almo2934-max/alexmozhaev-link-hub

Custom domain:
go.alexmozhaev.com

The DNS configuration has been verified directly in REG.RU. There is exactly one record for go:

CNAME go.alexmozhaev.com → almo2934-max.github.io.

TTL: 86400 seconds.

Google DNS and Cloudflare DNS both return the same CNAME with NOERROR.

There are no conflicting DNS records for go, and I found no evidence of CAA blocking or DNSSEC validation failures.

The repository CNAME file contains exactly: go.alexmozhaev.com

GitHub Pages Settings currently shows:

• DNS Check in Progress
• TLS provisioning: Step 1 of 3 — Certificate Requested
• Enforce HTTPS unavailable

HTTPS currently presents GitHub's default *.github.io certificate rather than a certificate covering go.alexmozhaev.com, resulting in a hostname mismatch.

The latest Pages workflow is:
https://github.com/almo2934-max/alexmozhaev-link-hub/actions/runs/37366316491

The build and deploy jobs completed successfully.
The report-build-status job was cancelled and the overall workflow result is failure.

The custom domain was already removed and re-added once on October 5, 2026, so I do not want to repeat that cycle without evidence that it is necessary.

The GitHub Support Portal reports “Technical support not included” for this account, so I am posting here as recommended for GitHub Free users.

Could a GitHub staff member or someone familiar with the Pages backend advise whether this provisioning state can become stuck internally and whether any server-side reset/retry is required?

Thank you.