GitHub Pages TLS certificate stuck in new state for verified custom domain

[Corentis-88]

Summary

The TLS certificate for my GitHub Pages custom domain appears to be stuck in GitHub's internal provisioning queue.

• Repository: https://github.com/Corentis-88/business-technology-hub
• Custom domain: thedigitalbusinesshub.co.uk
• Additional domain: www.thedigitalbusinesshub.co.uk
• Previous GitHub Support ticket: #4577470 (automatically closed without resolving the Pages issue)

Current GitHub Pages API state

{
  "protected_domain_state": "verified",
  "https_certificate": {
    "state": "new",
    "description": "This domain was recently added. The certificate request process will begin shortly.",
    "domains": [
      "thedigitalbusinesshub.co.uk",
      "www.thedigitalbusinesshub.co.uk"
    ]
  },
  "https_enforced": false
}

DNS configuration already verified

The apex domain points to all four documented GitHub Pages addresses:

• 185.199.108.153
• 185.199.109.153
• 185.199.110.153
• 185.199.111.153

The www record is a CNAME to corentis-88.github.io.

The GitHub domain-verification TXT record is present, and the domain is shown as verified in the GitHub account. There are no conflicting apex A/AAAA/CNAME records, no DNSSEC mismatch and no restrictive CAA record.

Independent HTTP-01 diagnostics for both the apex and www hostnames passed. HTTP serves the deployed Pages website correctly. HTTPS still presents GitHub's generic *.github.io certificate, which does not contain either custom hostname.

Troubleshooting already completed

• Removed and re-added the custom domain.
• Recreated the GitHub Pages site.
• Successfully redeployed using the official Pages Actions workflow.
• Verified the domain at account level using GitHub's TXT record.
• Reattached the verified domain and redeployed.
• Waited and repeatedly checked the Pages API; it remains in state: new.

The site itself is deployed successfully. The failure is limited to GitHub's custom-domain TLS provisioning job not progressing beyond new.

Could a GitHub Pages staff member please inspect and manually restart or requeue the TLS certificate-provisioning pipeline for this domain?

A similar stuck provisioning case was resolved after a GitHub staff member manually kicked the process here: https://github.com/orgs/community/discussions/31030

Thank you.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.