new release #134

New Issue

adam · 2025-12-29T00:25:35+01:00

adam commented

2025-12-29 00:25:35 +01:00

Originally created by @glensc on GitHub (Aug 4, 2016).

please make new release ASAP, since the old release contains old license url and client fails to work

# /usr/sbin/letsencrypt.sh -c
# INFO: Using main config file /etc/webapps/letsencrypt.sh/config.sh
+ Generating account key...
+ Registering account key with letsencrypt...
  + ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/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 [https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf]",
  "status": 400
}

it's fixed in master: afabfff06e
so just new release is needed!

Originally created by @glensc on GitHub (Aug 4, 2016). please make new release ASAP, since the old release contains old license url and client fails to work ``` # /usr/sbin/letsencrypt.sh -c # INFO: Using main config file /etc/webapps/letsencrypt.sh/config.sh + Generating account key... + Registering account key with letsencrypt... + ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/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 [https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf]", "status": 400 } ``` it's fixed in master: afabfff06e2dece1772ed788ac41ca0d297ab49b so just new release is needed!

adam closed this issue

2025-12-29 00:25:36 +01:00

adam commented

2025-12-29 00:25:36 +01:00

@lukas2511 commented on GitHub (Aug 20, 2016):

There are still a few things that I see as important for the next release, so... sorry, but this has to wait. Packagers can cherrypick this commit and most people use a fixed commit id or just master anyway.

@lukas2511 commented on GitHub (Aug 20, 2016): There are still a few things that I see as important for the next release, so... sorry, but this has to wait. Packagers can cherrypick this commit and most people use a fixed commit id or just master anyway.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#134