root
/
acme.js
mirror of https://github.com/therootcompany/acme.js
2
0
Fork 1
Code Issues 8 Releases Wiki Activity

UNHANDLED_ORDER_STATUS error #7

New Issue
Open
opened 2020-07-26 13:09:04 +00:00 by Ghost · 0 comments
Ghost commented 2020-07-26 13:09:04 +00:00
Copy Link

Hello

I noticed this new error today, FYI after I get this error ... the certificate is correctly generated and everything is working ... except it's renegerating the cert each time ...

(node:24266) UnhandledPromiseRejectionWarning: Error: Didn't finalize order: Unhandled status '403'. This is not one of the known statuses...
Requested: 'redacted.redacted.com'
Validated: ''
{
  "type": "urn:ietf:params:acme:error:orderNotReady",
  "detail": "Order's status (\"valid\") is not acceptable for finalization",
  "status": 403
}

Please open an issue at https://git.rootprojects.org/root/acme.js

Any idea about what is wrong?
Thanks a lot for your help and great library

Here is the full log

Loading existing ACME account...
Loading existing ACME account...
ACME ID:  https://acme-v02.api.letsencrypt.org/acme/acct/92343823
Loading existing serverKey ...
public Folder: /root/ws-trail//public/
validating domain authorization for redacted.redacted.com
INIT ACME CHALLENGE
SET ACME CHALLENGE
writing: /root/ws-trail/public/.well-known/acme-challenge/test-22cfaa7bebc3981c3f9f595fb2471404-0
ACME ID:  https://acme-v02.api.letsencrypt.org/acme/acct/92343823
Loading existing serverKey ...
public Folder: /root/ws-trail//public/
validating domain authorization for redacted.redacted.com
INIT ACME CHALLENGE
SET ACME CHALLENGE
writing: /root/ws-trail/public/.well-known/acme-challenge/test-08323081cc39d44789c2845a582457ac-0
config auto saved on disk
REMOVE ACME CHALLENGE
certificate_order
REMOVE ACME CHALLENGE
certificate_order
challenge_status redacted.redacted.com valid
REMOVE ACME CHALLENGE
wrote /root/ws-trail/CERTS/meta.json
challenge_status redacted.redacted.com valid
REMOVE ACME CHALLENGE
wrote /root/ws-trail/CERTS/meta.json
certificate_status  valid
certificate_status  403
(node:24266) UnhandledPromiseRejectionWarning: Error: Didn't finalize order: Unhandled status '403'. This is not one of the known statuses...
Requested: 'redacted.redacted.com'
Validated: ''
{
  "type": "urn:ietf:params:acme:error:orderNotReady",
  "detail": "Order's status (\"valid\") is not acceptable for finalization",
  "status": 403
}

Please open an issue at https://git.rootprojects.org/root/acme.js
    at Object.E.UNHANDLED_ORDER_STATUS (/root/ws-trail/node_modules/@root/acme/errors.js:28:9)
    at /root/ws-trail/node_modules/@root/acme/acme.js:1076:7
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async GenerateCert (/root/ws-trail/node_modules/@elestio/cloudgate/lib/letsencrypt.js:212:13)
(node:24266) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async functi                                      on without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise re                                      jection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id:                                       2)
(node:24266) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled                                       will terminate the Node.js process with a non-zero exit code.
Hello I noticed this new error today, FYI after I get this error ... the certificate is correctly generated and everything is working ... except it's renegerating the cert each time ... ``` (node:24266) UnhandledPromiseRejectionWarning: Error: Didn't finalize order: Unhandled status '403'. This is not one of the known statuses... Requested: 'redacted.redacted.com' Validated: '' { "type": "urn:ietf:params:acme:error:orderNotReady", "detail": "Order's status (\"valid\") is not acceptable for finalization", "status": 403 } Please open an issue at https://git.rootprojects.org/root/acme.js ``` Any idea about what is wrong? Thanks a lot for your help and great library Here is the full log ``` Loading existing ACME account... Loading existing ACME account... ACME ID: https://acme-v02.api.letsencrypt.org/acme/acct/92343823 Loading existing serverKey ... public Folder: /root/ws-trail//public/ validating domain authorization for redacted.redacted.com INIT ACME CHALLENGE SET ACME CHALLENGE writing: /root/ws-trail/public/.well-known/acme-challenge/test-22cfaa7bebc3981c3f9f595fb2471404-0 ACME ID: https://acme-v02.api.letsencrypt.org/acme/acct/92343823 Loading existing serverKey ... public Folder: /root/ws-trail//public/ validating domain authorization for redacted.redacted.com INIT ACME CHALLENGE SET ACME CHALLENGE writing: /root/ws-trail/public/.well-known/acme-challenge/test-08323081cc39d44789c2845a582457ac-0 config auto saved on disk REMOVE ACME CHALLENGE certificate_order REMOVE ACME CHALLENGE certificate_order challenge_status redacted.redacted.com valid REMOVE ACME CHALLENGE wrote /root/ws-trail/CERTS/meta.json challenge_status redacted.redacted.com valid REMOVE ACME CHALLENGE wrote /root/ws-trail/CERTS/meta.json certificate_status valid certificate_status 403 (node:24266) UnhandledPromiseRejectionWarning: Error: Didn't finalize order: Unhandled status '403'. This is not one of the known statuses... Requested: 'redacted.redacted.com' Validated: '' { "type": "urn:ietf:params:acme:error:orderNotReady", "detail": "Order's status (\"valid\") is not acceptable for finalization", "status": 403 } Please open an issue at https://git.rootprojects.org/root/acme.js at Object.E.UNHANDLED_ORDER_STATUS (/root/ws-trail/node_modules/@root/acme/errors.js:28:9) at /root/ws-trail/node_modules/@root/acme/acme.js:1076:7 at processTicksAndRejections (internal/process/task_queues.js:97:5) at async GenerateCert (/root/ws-trail/node_modules/@elestio/cloudgate/lib/letsencrypt.js:212:13) (node:24266) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async functi on without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise re jection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:24266) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
v1.x
bugfix-accept-pem
v3
v1
wip-v3
browser-v2
errors
v2
skip-valid-challenge
v1.8.7
v3.1.1
v3.0.10
v3.0.9
v3.0.8
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.2
v3.0.1
v1.8.6
v1.8.5
v1.8.4
v1.8.2
v1.8.1
v1.8.0
v1.7.7
v1.7.6
v1.7.5
v1.7.3
v1.7.2
v1.7.1
v1.6.0
v1.5.3
v1.5.2
v1.5.1
v1.5.0
v1.3.1
v1.3.0
v1.2.1
v1.2.0
v1.1.1
v1.1.0
v1.0.9
v1.0.8
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v0.6.2
v0.6.1
v0.6.0
v0.0.2
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: root/acme.js#7
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?