Like with the badNonce issue discussed in #17 - I am still encountering nonce value issues as of greenlock@2.8.2 and acme-v2@1.8.2.
I have not been able to determine the root cause, but retrying on a bad nonce seems to take care of the failure symptom so here is a patch for those annoying cases where it gets stuck on a domain.
[acme-v2] handled(?) rejection as errback:
Error: [acme-v2.js] authorizations were not fetched for '{{domain}}':
{"type":"urn:ietf:params:acme:error:badNonce","detail":"JWS has an invalid anti-replay nonce: \"{{nonce}}\"","status":400}
at /var/www/brand/node_modules/acme-v2/node.js:1180:10
at process._tickCallback (internal/process/next_tick.js:68:7)
[acme-v2] handled(?) rejection as errback:
Error: Didn't finalize order: Unhandled status '400'. This is not one of the known statuses...
Requested: '{{domain}}'
Validated: '{{domain}}'
{
"type": "urn:ietf:params:acme:error:badNonce",
"detail": "JWS has no anti-replay nonce",
"status": 400
}
Please open an issue at https://git.coolaj86.com/coolaj86/acme-v2.js
at /var/www/brand/node_modules/acme-v2/node.js:1005:6
at process._tickCallback (internal/process/next_tick.js:68:7)
Like with the `badNonce` issue discussed in #17 - I am still encountering nonce value issues as of `greenlock@2.8.2` and `acme-v2@1.8.2`.
I have not been able to determine the root cause, but retrying on a bad nonce seems to take care of the failure symptom so here is a patch for those annoying cases where it gets stuck on a domain.
```
[acme-v2] handled(?) rejection as errback:
Error: [acme-v2.js] authorizations were not fetched for '{{domain}}':
{"type":"urn:ietf:params:acme:error:badNonce","detail":"JWS has an invalid anti-replay nonce: \"{{nonce}}\"","status":400}
at /var/www/brand/node_modules/acme-v2/node.js:1180:10
at process._tickCallback (internal/process/next_tick.js:68:7)
```
```
[acme-v2] handled(?) rejection as errback:
Error: Didn't finalize order: Unhandled status '400'. This is not one of the known statuses...
Requested: '{{domain}}'
Validated: '{{domain}}'
{
"type": "urn:ietf:params:acme:error:badNonce",
"detail": "JWS has no anti-replay nonce",
"status": 400
}
Please open an issue at https://git.coolaj86.com/coolaj86/acme-v2.js
at /var/www/brand/node_modules/acme-v2/node.js:1005:6
at process._tickCallback (internal/process/next_tick.js:68:7)
```
Like with the
badNonce
issue discussed in #17 - I am still encountering nonce value issues as ofgreenlock@2.8.2
andacme-v2@1.8.2
.I have not been able to determine the root cause, but retrying on a bad nonce seems to take care of the failure symptom so here is a patch for those annoying cases where it gets stuck on a domain.
Closing as abandoned.
プルリクエストはクローズされました