Hi! I asked Github for help on this, and they just pointed me to a Service Disruption on your end, so I thought I'd reach out over here.
My domain is: haddleton.me
I ran this command: N/A, Github TLS GUI
It produced this output: "Certificate Request Error: Certificate provisioning will retry automatically in a short period, please be patient."
My web server is (include version): N/A
The operating system my web server runs on is (include version): N/A
My hosting provider, if applicable, is: Github
I can login to a root shell on my machine (yes or no, or I don't know): I don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot): N/A
I'm not familiar with Github hosting, I've just used Github for commenting on issues and an occasional pull request. Is this some built-in interface that requests certificates on your behalf and that error is all that you see? If so, I think it has to be something on their side.
The only current issue is with the test certificate transparency system (Testflume). Other than that, the last issue was a couple days ago. Actual normal certificate issuance should be working fine.
It's possible that they're checking the status API but not actually checking which Let's Encrypt service is down. The Testflume outage has been happening for a month now and I don't see any indication of when it might be back up, so if that's what's stopping them they need to work on fixing their system to only look at the status of the certificate issuance and not the test Let's Encrypt services. That's all just a semi-educated guess as to what's happening, though.
Correct, it's a built-in interface that requests certs for domains attached to their hosting service.
I've relayed this information back to Github Support - if I hear anything more, I'll follow up here. Thanks!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.