Custom domain fancato.com — HTTPS certificate never provisions (stuck)

[couespelb-stack]

🏷️ Discussion Type

Bug

Body

My GitHub Pages custom domain never gets an HTTPS certificate — it's been stuck for several days.

• Repository: couespelb-stack/fancato (public)
• Custom domain: fancato.com (apex)
• Pages source: branch main, root
• Served fine over HTTP (200); CNAME file present in the repo.
• DNS correct: fancato.com → the 4 GitHub Pages A records (185.199.108–111.153), verified via 8.8.8.8.
• No CAA, no AAAA, no Cloudflare proxy (nameservers at OVH, pointing directly to GitHub's IPs).
• "Enforce HTTPS" is greyed out; certificate status never changes. The API returns https_certificate: null (state: none).
• Already removed and re-added the custom domain several times — no change.

Could a GitHub staff member please re-trigger the Let's Encrypt certificate provisioning for fancato.com? Everything on my side matches the documented requirements. 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. ⭐

[chowdhary19]

@couespelb-stack Your DNS setup already appears to meet GitHub Pages’ documented requirements. Since the site works over HTTP, Enforce HTTPS is still disabled, and the certificate state remains none after several days, this likely needs GitHub Support to inspect the certificate provisioning state.

GitHub notes that DNS changes can take up to 24 hours to propagate, but you are already well beyond that window.

What to do

1. Stop removing and re-adding the domain, since that may restart the provisioning process.
2. Take screenshots of:
   • Repository → Settings → Pages
   • your OVH DNS records
   • the API response showing https_certificate: null
3. Open GitHub Support:
   https://support.github.com/
4. Sign in, create a ticket for GitHub Pages / Custom domain / HTTPS, and send:

Hi GitHub Support,

My GitHub Pages custom domain has been unable to obtain an HTTPS certificate for several days.

Repository: couespelb-stack/fancato
Custom domain: fancato.com
Pages source: main, repository root
Certificate API status: https_certificate: null, state none

I have verified that:

• The apex domain points to GitHub Pages’ four documented A records.
• DNS resolves correctly through public resolvers.
• There are no AAAA, CAA, wildcard, or Cloudflare proxy records.
• The CNAME file contains only fancato.com.
• The site works correctly over HTTP.
• Enforce HTTPS remains unavailable after several days.

Could you please inspect the Pages certificate state and re-trigger certificate provisioning if necessary?

Thank you.

GitHub’s documentation also recommends checking the repository’s Pages settings and its custom-domain troubleshooting guidance when certificate creation does not complete.

[couespelb-stack]

Thanks @chowdhary19! I already opened a Support ticket (#4555466) but it was automatically closed by the bot (free plan → no human ticket support). Since everything on my side matches the documented requirements and the certificate has been stuck at state "none" for several days, could a GitHub staff member please inspect the Pages certificate state for fancato.com and re-trigger provisioning directly? I've stopped removing/re-adding the domain as advised. Thank you!