[jaas]

Let's Encrypt has been working normally for most of the day. There was a ~90 minute period during which some of our users would have received a higher error rate due to upstream networking issues, but the majority of requests were successful even during that period.

It seems our status.io notes are being misinterpreted as much more severe than they were intended to reflect.

Edit: Note that this was written in response to a previous submission title implying that Let's Encrypt was entirely down most of the day.

[widdakay]

I'm not sure if your higher error rate is sticky per user or something, but I've tried 10+ times throughout the day and have had 0 successes. They all come back as internal server error. That's why I eventually posted.

[jaas]

It would not have been sticky for the entire day. If it was sticky at all, it would have been only during the 90 minute period I referenced. It's most likely that there is some other issue with how you're requesting the cert. Folks can help debug at: https://community.letsencrypt.org/

[widdakay]

I ran the exact same command now and it's working, so it is possible I was unlucky and was hitting all the worst possible cases.

[sgt]

Could it be that he was simply throttled while retrying? That seems plausible, and it would make it seem like a long outage.

[widdakay]

I updated the post title to say (Fixed) now.

[jaas]

Since Let's Encrypt wasn't down most of the day if would be helpful if you could update the title to reflect that.

[widdakay]

I updated the title. Let me know if you think it's more accurate. It did appear as down for me though.

[jaas]

Yeah, thanks

[teekert]

Why are you trying? Doesn’t Caddy (or something) just takes care of this well in advance and should have no issues with one or several days of my service at all at any time?

Edit: my bad. I’ve tried as well recently, when you’re rushing to get your new domain up of course…