GitHub Pages custom domain DNS check successful but HTTPS certificate is not issued

[PetrovMAndrey]

🏷️ Discussion Type

Bug

Body

Hello,

I am using GitHub Pages with a custom domain:

ark-culture.ru

Repository:
https://github.com/PetrovMAndrey/ARK-CULTURE

Current status:

• Custom domain is configured
• DNS check successful
• Website works via HTTP
• DNS propagation completed more than 72 hours ago
• GitHub Pages Virtual Assistant reports "Everything looks good"

However HTTPS is still unavailable.

GitHub Pages shows:

"Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS"

When opening https://ark-culture.ru the browser reports an invalid certificate and HTTPS does not work.

I have already verified DNS records and GitHub Pages configuration.

Could someone please help determine why the SSL certificate for ark-culture.ru has not been issued?

Thank you.

[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. ⭐

[tanvishinde017]

Hello,

If DNS propagation has already completed and the site works over HTTP, then the issue is often related to one of these situations:

1. Old or conflicting DNS records

   • Make sure there are no additional A, AAAA, CNAME, or CDN records pointing somewhere other than GitHub Pages.
   • Old records from previous hosting providers can prevent certificate issuance.

2. CAA records

   • If your domain uses CAA records, verify that they allow Let's Encrypt, since GitHub Pages certificates are issued through Let's Encrypt.

3. Temporary certificate provisioning delay

   • Sometimes removing the custom domain from the repository settings, waiting a few minutes, and then adding it again can trigger a new certificate request.

4. Incorrect www/root configuration

   • Verify that both ark-culture.ru and www.ark-culture.ru are configured consistently and that only one is set as the custom domain in GitHub Pages.

5. Existing invalid certificate

   • A previously issued certificate from another provider may occasionally interfere until DNS records fully point to GitHub.

If possible, could you share the current DNS records for:

• ark-culture.ru
• www.ark-culture.ru

(including A, AAAA, CNAME, and CAA records)

That information would help determine why GitHub Pages is still reporting that HTTPS cannot be enabled.