If dehydrated does a fetch from an acme server, and the transaction is completed using HTTP/2, the returned headers may not be in the same case (e.g. may be all lower case) as the script is grepping for.
dehydrated-io/dehydrated@e4e712c
Output when this happens includes:
+ Requesting challenge for x.y.org...
+ ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/new-authz (Status 400)
Details:
{
"type": "urn:acme:error:badNonce",
"detail": "JWS has no anti-replay nonce",
"status": 400
}
Could this package be updated? In addition to this bug fix, it appears to include new features like wildcard support and alpn validation.
If dehydrated does a fetch from an acme server, and the transaction is completed using HTTP/2, the returned headers may not be in the same case (e.g. may be all lower case) as the script is grepping for.
dehydrated-io/dehydrated@e4e712c
Output when this happens includes:
Could this package be updated? In addition to this bug fix, it appears to include new features like wildcard support and alpn validation.