githubRover

If those two curl requests fail it is a problem with your comms outbound from your server. Yes, it would be an issue with your hosting company. I was expecting...

If wget always works and curl always fails part of your network stack is messed up. That is very unusual. In any case, this problem isn't unique to getssl or...

There were recent changes to revocation reasons in Let's Encrypt. This topic in their community is helpful to guide any changes to getssl https://community.letsencrypt.org/t/questions-re-upcoming-changes-to-revocation-reasons/182954

Required for ZeroSSL and relatively new Google CA support for ACME too

As further background to this error the LE system was having problems. From history at `https://letsencrypt.status.io/ ` November 11, 2022 05:21 UTC[Resolved] We have resolved the issue and traffic patterns...

As a workaround you could just do a manual install (I use just the single getssl.sh script) https://github.com/srvrco/getssl#manual-installation

Not to dissuade you from ARI but it is not trivial to implement. And, the specs are young enough to still be evolving. Here's a few recent discussions from the...

Just fyi Let's Encrypt Staff made announcement today about significant ARI spec changes https://community.letsencrypt.org/t/discontinuing-support-for-acme-clients-using-draft-ietf-acme-ari-01/215126

Do you block access by geographic region or countries? Because Let's Encrypt recently added two additional remote validation server locations. The "secondary validation" points to a problem with one of...

Where do you see that error? If your last good cert was before Feb8 of this year I would guess that the system reporting the error does not have ISRG...