GitHub Pages HTTPS certificate issue for volt71.ru

[semenoffdani-cmyk]

🏷️ Discussion Type

Bug

Body

Hello,

My GitHub Pages site is published from the repository semenoffdani-cmyk/volt71-site.

My custom domain is volt71.ru. In Settings → Pages, the DNS check says “DNS check successful”, but “Enforce HTTPS” is unavailable because the domain is not properly configured to support HTTPS.

Safari shows an invalid certificate warning when I open https://volt71.ru.

My DNS records are the four GitHub Pages A records:

• 185.199.108.153
• 185.199.109.153
• 185.199.110.153
• 185.199.111.153

I also have a CNAME record for www.volt71.ru pointing to semenoffdani-cmyk.github.io. There are no AAAA records.

I have already removed and re-added the custom domain in GitHub Pages settings, but HTTPS is still unavailable.

Could someone advise how to resolve the HTTPS certificate provisioning issue?

Thank you.

Update: I tested www.volt71.ru using SSL Labs.

All four GitHub Pages IPv4 addresses (185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153) and the four GitHub Pages IPv6 addresses return “Certificate not valid for domain name”.

GitHub Pages still shows “DNS check successful”, but “Enforce HTTPS” remains unavailable. I have already removed and re-added the custom domain once.

Could someone advise whether the TLS certificate provisioning for volt71.ru and www.volt71.ru is stuck or requires another step?

Additional DNS findings:

• volt71.ru has no CAA records.
• www.volt71.ru is a CNAME to semenoffdani-cmyk.github.io.
• The CAA records returned for the CNAME target include 0 issue "letsencrypt.org" and 0 issuewild "letsencrypt.org".
• GitHub Pages still reports “DNS check successful”, but “Enforce HTTPS” remains unavailable.
• SSL Labs reports “Certificate not valid for domain name” for the GitHub Pages IP addresses.

I have already removed and re-added the custom domain once. Could someone advise what else could prevent certificate provisioning?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[RizgarOzan]

Your apex actually does have an AAAA record. volt71.ru resolves to 2a03:6f00:1::5c35:60df, which isn't a GitHub address (probably a default from your DNS host). You can check with:

nslookup -type=AAAA volt71.ru

The HTTPS docs list extra A/AAAA records on the apex that don't point at Pages as a reason the certificate can't be issued. Right now https://volt71.ru over IPv4 serves the generic *.github.io cert, so nothing has been provisioned for your domain.

Delete that AAAA record at your DNS host. If you want IPv6, use GitHub's four instead: 2606:50c0:8000::153 through 2606:50c0:8003::153. Then in Settings → Pages remove the custom domain, save, and add it back to restart provisioning. It can take up to an hour or so before "Enforce HTTPS" unlocks.

[BenkhiraAhmedBaderEddine1]

Hi,

Based on your checks, the DNS configuration looks correct, and the fact that both hostnames return a certificate-name mismatch suggests that the custom-domain TLS certificate may not have been provisioned or deployed correctly.

I'd recommend checking the repository's CNAME configuration, confirming that no conflicting DNS records exist, and keeping the DNS settings unchanged while troubleshooting.

Since you've already removed and re-added the custom domain, I wouldn't keep repeating that step. If the issue persists beyond the normal provisioning window, contact [GitHub Support](https://support.github.com/contact) and ask them to investigate the certificate provisioning status for both volt71.ru and www.volt71.ru.

Include the repository name, the date you last re-added the domain, the successful DNS check, the SSL Labs hostname-mismatch results, and the certificate's Subject Alternative Name output. This should help distinguish a DNS problem from a certificate provisioning or deployment issue.

Official troubleshooting documentation:
https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https

Hope this helps!