GitHub Pages – Enforce HTTPS Unavailable Despite Successful DNS Verification #213223
Replies: 2 comments
|
Hi @Bailasanzaina, Since GitHub Pages already reports "DNS check successful", but "Enforce HTTPS" remains disabled, the issue may be related to TLS certificate provisioning rather than the basic DNS configuration. I recommend checking the following: 1. Verify DNS records from the terminal dig bailasanzaina.com A +short
dig bailasanzaina.com AAAA +short
dig www.bailasanzaina.com CNAME +short
dig bailasanzaina.com CAA +shortThe apex domain should resolve to GitHub Pages' IP addresses: The Make sure there are no conflicting A, AAAA, ALIAS, ANAME, or wildcard DNS records. If CAA records exist, they must permit 2. Check the HTTPS certificate Run: curl -Iv https://bailasanzaina.comCheck whether the certificate matches your custom domain or whether GitHub is still serving a certificate for another hostname. 3. Check GitHub Pages configuration Navigate to: Repository → Settings → Pages Verify that the custom domain is exactly 4. Allow certificate provisioning to complete GitHub automatically requests a Let's Encrypt certificate after successful DNS validation. GitHub's documentation notes that HTTPS availability can take up to an hour after configuration. Since you have already removed and re-added the domain, I would avoid repeatedly restarting the process. 5. Escalate if the issue persists If the DNS records are correct, propagation is complete, and HTTPS is still unavailable after 24 hours, I recommend contacting GitHub Support with the domain, repository URL, DNS output, and TLS error. It may require investigation of the certificate provisioning process on GitHub's side. Official documentation: Hope this helps! |
|
Hi @Bailasanzaina, Since you've already completed domain ownership verification and GitHub Pages reports "DNS check successful," I would focus on the HTTPS certificate provisioning stage rather than repeating the TXT verification process. GitHub Pages uses Let's Encrypt to request and provision TLS certificates after its DNS validation succeeds. Therefore, successful DNS verification does not necessarily mean that the certificate has already been issued and deployed. I'd recommend checking a few additional things: 1. Verify all DNS recordsFor The Make sure there are no conflicting or stale 2. Check DNS propagation independentlyYou can use these commands: dig bailasanzaina.com A
dig bailasanzaina.com AAAA
dig www.bailasanzaina.com CNAME
dig bailasanzaina.com CAAAlternatively, on Windows PowerShell: Resolve-DnsName bailasanzaina.com -Type A
Resolve-DnsName bailasanzaina.com -Type AAAA
Resolve-DnsName www.bailasanzaina.com -Type CNAME
Resolve-DnsName bailasanzaina.com -Type CAAPay particular attention to unexpected DNS records and whether the results are consistent across DNS resolvers. 3. Check CAA recordsEven if there are no restrictive CAA records currently visible, it's worth verifying the authoritative DNS response. If your domain has CAA records, ensure that they authorize Let's Encrypt ( 4. Allow sufficient time for certificate provisioningAccording to GitHub's documentation, after successful DNS validation, GitHub queues a certificate request. Provisioning and deployment can take time. Avoid repeatedly removing and re-adding the custom domain. If provisioning remains stuck, GitHub recommends removing and re-adding the domain to restart the process. 5. If the problem persistsIf the DNS configuration is correct and HTTPS is still unavailable after 24 hours, I would recommend contacting GitHub Support. Include:
They may need to investigate whether certificate issuance or deployment is stuck on the GitHub Pages side. One question: How long has the DNS check been showing successful while the Enforce HTTPS option remains disabled? This would help distinguish a normal certificate provisioning delay from a potentially stuck provisioning process. Hope this helps! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
Hello GitHub Community,
I'm experiencing an issue enabling HTTPS for my personal academic website hosted on GitHub Pages.
Domain: bailasanzaina.com
Repository: https://github.com/Bailasanzaina/bailasanzaina.github.io
My website is successfully deployed, and GitHub Pages displays "DNS check successful." However, the Enforce HTTPS checkbox remains disabled with the following error:
"Unavailable for your site because your domain is not properly configured to support HTTPS."
Troubleshooting completed:
wwwCNAME to point tobailasanzaina.github.io.Despite these steps, HTTPS remains unavailable.
Could someone help determine whether there is an issue with certificate provisioning or whether I need to adjust any additional settings?
Thank you for your help!
All reactions