GitHub Pages certificate request error for helloyang.loc.cc after 34 hours #213528
Replies: 3 comments
|
I checked the live DNS and HTTP setup for
The reason both your domain and
Options right now:
|
|
I rechecked a few things from outside, so this is what I can confirm versus what's still a guess. Confirmed:
Still a hypothesis: nobody outside GitHub can see the actual ACME response, so "rate limited" is the most likely cause, not a proven one. Your DNS side looks correct, so I wouldn't change anything there. What I'd do:
|
|
💬 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. ⭐ |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
GitHub Pages has deployed successfully for
helloyang.loc.cc, and the site responds with HTTP 200. I expected HTTPS to become available after the DNS check passed, but Pages still shows step 1 of 3 andCertificate Request Error. The Enforce HTTPS checkbox is disabled.185.199.108.153,185.199.109.153,185.199.110.153, and185.199.111.153.wwwis a CNAME toyxt666777.github.io. Pages reportsDNS check successful.loc.cchostname. This domain already uses the four explicit A records discussed in that thread.Could GitHub staff check the underlying ACME error for this hostname and let me know whether there is anything I need to change? Thanks.
All reactions