TLS certificate is being provisioned. This may take up to 15 minutes to complete. #176744
-
Select Topic AreaQuestion BodyTLS certificate is being provisioned. This may take up to 15 minutes to complete. All "A" records are fine. CNAME is configured correctly. I deleted all the settings and added them again. What could be the problem? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This message usually means GitHub Pages has detected your custom domain but has not yet been able to verify it through DNS for SSL provisioning. Even if your A and CNAME records look correct, the DNS changes might not have fully propagated through the global network. You can confirm the setup by running If it remains stuck after another full day, open a ticket with GitHub Support and include the output from your DNS queries. They can check whether the certificate provisioning service failed internally. If this helps fix your issue, please mark the answer as helpful so others can find it easily. |
Beta Was this translation helpful? Give feedback.
This message usually means GitHub Pages has detected your custom domain but has not yet been able to verify it through DNS for SSL provisioning. Even if your A and CNAME records look correct, the DNS changes might not have fully propagated through the global network.
You can confirm the setup by running
dig yourdomain.comanddig www.yourdomain.comfrom a terminal. Both should return GitHub’s IP addresses (185.199.108.0/22) or the correct CNAME foryourusername.github.io. If the records look right but GitHub still shows “TLS certificate is being provisioned” after more than 24 hours, remove the custom domain from your repository settings, wait about 10 minutes, and then re-add it. This tr…