GitHub Pages custom domain validation and HTTPS certificate provisioning stuck

[najuatech]

🏷️ Discussion Type

Bug

Body

Hello

I am having trouble enabling HTTPS for my GitHub Pages custom domain, najuatech.co.tz, on the repository najuatech/najuatech.github.io.

The DNS configuration has been checked against GitHub's documented requirements:

• Apex A records point to all four recommended GitHub Pages IPv4 addresses:
  • 185.199.108.153
  • 185.199.109.153
  • 185.199.110.153
  • 185.199.111.153
• The www CNAME points to najuatech.github.io.
• No conflicting apex AAAA or wildcard records were found.
• The repository's CNAME file contains najuatech.co.tz.
• The repository's GitHub Pages settings use najuatech.co.tz as the custom domain.

Both the apex and www domain reach GitHub Pages. However, HTTPS presents a default *.github.io certificate rather than a certificate covering najuatech.co.tz and www.najuatech.co.tz.

I have already removed and re-added the custom domain once, but the problem remains.

Could you please investigate the Pages domain validation and certificate provisioning status for this repository, and help issue the correct custom-domain certificate?

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

[najuatech]

Hello GitHub Support,

I'm following up on my existing support request regarding HTTPS for my GitHub Pages custom domain, najuatech.co.tz.

I have completed additional diagnostics and confirmed that GitHub Pages is serving the website, but the TLS certificate presented does not cover my custom domain.

Configuration and DNS

• GitHub Pages repository: najuatech/najuatech.github.io
• Custom domain configured in Pages settings: najuatech.co.tz
• The live main branch contains a root-level CNAME file with exactly najuatech.co.tz.
• The apex DNS A records point to GitHub Pages:
  • 185.199.108.153
  • 185.199.109.153
  • 185.199.110.153
  • 185.199.111.153
• The www hostname has a CNAME pointing to najuatech.github.io.

Diagnostic results

A request to https://najuatech.co.tz/ with normal certificate verification fails:

curl: (60) SSL: no alternative certificate subject name matches target host name 'najuatech.co.tz'

When certificate verification is bypassed using curl -k, the server returns:

HTTP/2 200
server: GitHub.com

The certificate currently presented has:

• Subject: CN=*.github.io
• Issuer: Let's Encrypt YR1
• Validity: September 30, 2026 – December 29, 2026
• Subject Alternative Names: *.github.com, *.github.io, *.githubusercontent.com, github.com, github.io, githubusercontent.com

Neither najuatech.co.tz nor www.najuatech.co.tz appears in the certificate SAN list.

I also attempted to verify the GitHub Pages domain-verification TXT record through public DNS resolvers and the domain's authoritative nameservers, but those TXT queries timed out. Therefore, I cannot confirm whether that record is publicly visible.

Please investigate:

1. Whether najuatech.co.tz is correctly verified and associated with my GitHub account and Pages repository.
2. Whether there is a pending or failed GitHub Pages custom-domain certificate issuance or renewal.
3. Whether any domain-verification or certificate-provisioning error is preventing HTTPS from becoming active.
4. What exact action, if any, is required from me or my DNS provider.

The website itself is reachable through GitHub Pages. The outstanding issue is the certificate hostname mismatch.

Thank you for your assistance.