What's the difference between urn:acme:error:serverInternal and urn:ietf:params:acme:error:serverInternal?
(Other than "ietf:params:" and that the latter is mentioned in RFC 8555 while the former is not.)
What's the difference between urn:acme:error:serverInternal and urn:ietf:params:acme:error:serverInternal?
(Other than "ietf:params:" and that the latter is mentioned in RFC 8555 while the former is not.)
You've actually just found a bug in our configuration!
V1ErrorNS = "urn:acme:error:"
V2ErrorNS = "urn:ietf:params:acme:error:
In the pre-RFC-8555-standardized ACME, the error namespace was urn:acme:error
. It should be urn:ietf:params:acme:error:
everywhere now.
However, our front-end load balancer rejects requests during outages (see ongoing incident https://letsencrypt.status.io/) with the V1 error.
We'll update that error message to use the correct RFC-standard error.
Thank you very much! I'll set our system to treat these as the same for now.
You'd normally never see this, but during the incident our load balancers and CDN configs got out of sync, so the CDN was directing traffic to "down" load balancers which have a static failure handler page which wasn't updated with the RFC error code
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.