Persistent SSL provisioning failure on rajanwedsriya.work.gd (State-sync/Revocation loop) #188616
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions