Originally created by @maxburke on GitHub (Sep 24, 2022).
I've been using dehydrated reliably for years, but noticed today when I went to renew some certs that the requests are failing with:
```
+ ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-order (Status 400)
Details:
HTTP/2 400
server: nginx
date: Sat, 24 Sep 2022 00:20:50 GMT
content-type: application/problem+json
content-length: 107
boulder-requester: 609382046
cache-control: public, max-age=0, no-cache
link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
replay-nonce: 0101NNOevri97g8xtGCk0ljInrw7lgEUwLPOPHDbhXCpWX0
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "JWS verification error",
"status": 400
}
```
Any idea what the culprit may be?
FWIW I worked around this by deleting the certs/accounts directory for the domains. I guess the key got out of sync or something?
@maxburke commented on GitHub (Sep 24, 2022):
FWIW I worked around this by deleting the `certs/accounts` directory for the domains. I guess the key got out of sync or something?
I was getting tons of errors on staging (had numerous downtime periods) and one of two production endpoints were down at one point or another. Just a heads-up for anyone with errors recently.
@Elkenfugel commented on GitHub (Oct 31, 2022):
Let's Encrypt had planned downtime on Oct 23, 2022 that got moved to this weekend:
October 28, 2022 20:00 - October 31, 2022 20:00 UTC
https://letsencrypt.status.io/pages/55957a99e800baa4470002da
I was getting tons of errors on staging (had numerous downtime periods) and one of two production endpoints were down at one point or another. Just a heads-up for anyone with errors recently.
i cannot remembered the place to specific the challenge url.. by example to use acme-v02.api.letsencrypt.org event the default https://acme-v02.api.letsencrypt.org
@mckaygerhard commented on GitHub (May 3, 2024):
i cannot remembered the place to specific the challenge url.. by example to use acme-v02.api.letsencrypt.org event the default https://acme-v02.api.letsencrypt.org
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @maxburke on GitHub (Sep 24, 2022).
I've been using dehydrated reliably for years, but noticed today when I went to renew some certs that the requests are failing with:
Any idea what the culprit may be?
@maxburke commented on GitHub (Sep 24, 2022):
FWIW I worked around this by deleting the
certs/accountsdirectory for the domains. I guess the key got out of sync or something?@krbvroc1 commented on GitHub (Oct 28, 2022):
I got this today for the first time:
@Elkenfugel commented on GitHub (Oct 31, 2022):
Let's Encrypt had planned downtime on Oct 23, 2022 that got moved to this weekend:
October 28, 2022 20:00 - October 31, 2022 20:00 UTC
https://letsencrypt.status.io/pages/55957a99e800baa4470002da
I was getting tons of errors on staging (had numerous downtime periods) and one of two production endpoints were down at one point or another. Just a heads-up for anyone with errors recently.
@mckaygerhard commented on GitHub (May 3, 2024):
i cannot remembered the place to specific the challenge url.. by example to use acme-v02.api.letsencrypt.org event the default https://acme-v02.api.letsencrypt.org