-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate status check for letsencrypt.org API to diagnose failures #311
Comments
👋 @kd8ssq I'm not a developer/user of Certify and may be incorrect, but I suspect this may be caused by a maintenance outage with the Let's Encrypt service. We expect service to be restored in the coming hour. Please keep an eye on letsencrypt.status.io for more. |
@cpu I believe you're correct. Thanks for the maintenance link. I was looking for it to see what the status of the services was but couldn't find it. I'll wait till things are restored then try again. |
@cpu I can confirm that was the issue. I subscribed for the updates to be notified when there's going to be an outage. Thanks again. @webprofusion-chrisc Is there a way to check the status of the Let's Encrypt servers prior to registering? Or maybe pull in the status feed into the settings area? Just a thought. |
@kd8ssq Great, glad to hear you're all set now. Thanks! |
@kd8ssq @cpu thanks folks, yes it would be great if the status.io sevice had an api for general use- perhaps its does? While we could parse the html I'd rather get a json feed. On the other hand it could result in significant traffic to the status.io api and I'm not sure what limits they have. Definitely something to look at. |
Further to this I plan to eventually use the letsdebug.net API to provide general 2nd level diagnostics. |
I'm getting an error when registering both a new cert and trying to renew an old cert. You can see the logs below. I'm wondering if it has to do with a communication issue between Certify and Let's Encrypt because it's happening on 2 different servers on both a new request and a renewal request. Am I correct? If so, would it be possible to add error handling to make a friendler error message so people know what the issue actually is?
The text was updated successfully, but these errors were encountered: