Skip to content
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

403 Finalize Error on Renewal #33

Open
nwesoccer opened this issue Aug 19, 2020 · 0 comments
Open

403 Finalize Error on Renewal #33

nwesoccer opened this issue Aug 19, 2020 · 0 comments

Comments

@nwesoccer
Copy link

We've had this running for a couple years now without issue, but it seems we are now getting 403 Forbidden on the finalize step when the certificates go to renew. Is anyone else getting this?

Seems to be coming from: https://github.com/ocelotconsulting/node-acme-lambda/blob/master/src/acme/v2/newCertificate.js#L13

INFO The error was {"req":{"method":"POST","url":"https://acme-v02.api.letsencrypt.org/acme/finalize/***obfuscated***/***obfuscated***","data":{"protected":"***obfuscated***"},"headers":{"content-type":"application/jose+json"}},"header":{"server":"nginx","date":"Wed, 19 Aug 2020 14:39:09 GMT","content-type":"application/problem+json","content-length":"152","connection":"close","boulder-requester":"obfuscated","cache-control":"public, max-age=0, no-cache","link":"https://acme-v02.api.letsencrypt.org/directory;rel="index"","replay-nonce":"obfuscated"},"status":403,"text":"{\n "type": "urn:ietf:params:acme:error:orderNotReady",\n "detail": "Order's status (\"invalid\") is not acceptable for finalization",\n "status": 403\n}"}

thenickdude added a commit to thenickdude/node-letsencrypt-lambda that referenced this issue Jul 14, 2022
Avoids these errors, which are caused by attempting to issue certs before records have propagated to all Route53 servers:

{
  "type": "urn:ietf:params:acme:error:orderNotReady",
  "detail": "Order's status (\"invalid\") is not acceptable for finalization",
  "status": 403
}

Fixes ocelotconsulting#33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant