no error recover on license mismatch #73

New Issue

adam · 2025-12-29T00:24:17+01:00

adam commented

2025-12-29 00:24:17 +01:00

Originally created by @ibukanov on GitHub (Mar 7, 2016).

This is similar to #2 . I am testing against own instance of boulder running at 192.168.95.14:4000. When I run letsencrypt.sh -c for the first time, I got an error:

  + ERROR: An error occurred while sending post-request to http://192.168.95.14:4000/acme/new-reg (Status 400)

Details:
{"type":"urn:acme:error:malformed","detail":"Provided agreement URL [https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf] does not match current agreement URL [http://192.168.95.14:4001/terms/v1]","status":400}

After I changed the config.sh to set LICENSE to point to the test server and run letsencrypt.sh -c, I got

  + ERROR: An error occurred while sending post-request to http://192.168.95.14:4000/acme/new-authz (Status 403)

Details:
{"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}

That is, there were no attempts to try to register again after the previous failed attempt. To recover I had to delete private_key.pem.

Originally created by @ibukanov on GitHub (Mar 7, 2016). This is similar to #2 . I am testing against own instance of boulder running at 192.168.95.14:4000. When I run `letsencrypt.sh -c` for the first time, I got an error: ``` + ERROR: An error occurred while sending post-request to http://192.168.95.14:4000/acme/new-reg (Status 400) Details: {"type":"urn:acme:error:malformed","detail":"Provided agreement URL [https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf] does not match current agreement URL [http://192.168.95.14:4001/terms/v1]","status":400} ``` After I changed the config.sh to set LICENSE to point to the test server and run letsencrypt.sh -c, I got ``` + ERROR: An error occurred while sending post-request to http://192.168.95.14:4000/acme/new-authz (Status 403) Details: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403} ``` That is, there were no attempts to try to register again after the previous failed attempt. To recover I had to delete `private_key.pem`.

adam closed this issue

2025-12-29 00:24:17 +01:00

adam commented

2025-12-29 00:24:18 +01:00

@lukas2511 commented on GitHub (Mar 9, 2016):

also slightly related to #92

@lukas2511 commented on GitHub (Mar 9, 2016): also slightly related to #92

adam referenced this issue

2025-12-29 01:28:32 +01:00

[PR #73] [CLOSED] Also concatenate privkey.pem and cert.pem to to privcert.pem. This is needed for e.g. pure-ftpd #701

Sign in to join this conversation.