Persistent SSL provisioning failure on rajanwedsriya.work.gd (State-sync/Revocation loop)

[lazyengineer-ai]

Select Topic Area

Bug

Body

Hi team, I am experiencing a persistent issue where my custom domain rajanwedsriya.work.gd successfully provisions a TLS certificate but loses it after ~2-3 hours, resulting in an ERR_SSL_PROTOCOL_ERROR.

Diagnostic Data:

CNAME File: Present in the root of the main branch (contains only rajanwedsriya.work.gd).

DNS Records: * 4 A-records pointed to GitHub IPs (185.199.108.153 through .111.153).

www CNAME pointed to lazyengineer-ai.github.io.

Verified: No AAAA (IPv6) or CAA records are present at the registrar.

Troubleshooting: Removing and re-adding the domain in the UI fixes the issue for exactly one certificate cycle (approx. 15 hours) before it is revoked.

It feels like the background verification job is failing its second pass. Could a staff member please check the internal logs for this domain or manually trigger a permanent certificate issuance?

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

[itxashancode]

I'd check if your DNS provider or a proxy like Cloudflare is intercepting the ACME challenge. GitHub's Let's Encrypt integration often drops certificates when the HTTP-01 validation fails on the second pass. Make sure your A records aren't behind any proxy or WAF that strips challenge requests.

I ran into this exact loop before. The fix was to delete the CNAME file, push an empty commit, then remove and re-add the domain in your repository Settings. After that, run dig rajanwedsriya.work.gd +short and verify it returns exactly those four GitHub IPs with no extra records.

Also open the CNAME file in a plain text editor and confirm it contains just rajanwedsriya.work.gd with no trailing spaces or newlines. GitHub's validation script is strict about that.

I'm not 100% sure if your registrar applies hidden rate limits to Let's Encrypt, but if the loop continues, lower the DNS TTL to 300 seconds before re-adding the domain. That gives the background job enough time to finish the second verification pass.