DirectAdmin: Provided agreement URL doesn't match current agreement URL

Hi there,

When trying to get new SSL certificates today I get this response:

User let’s encrypt key has been found, but not registered. Registering…
Account registration error. Response: HTTP/1.1 100 Continue
Expires: Thu, 16 Nov 2017 13:30:45 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 267
Replay-Nonce: VhrlLN3RIw–8WdDcU0LXvlIMhdaV88r_z7rpTnXrgI
Expires: Thu, 16 Nov 2017 13:30:45 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Thu, 16 Nov 2017 13:30:45 GMT
Connection: close

{
“type”: “urn:acme:error:malformed”,
“detail”: “Provided agreement URL [https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf] does not match current agreement URL [https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf]”,
“status”: 400
}.

What exactly does this mean?

Thanks.

Hi @jerrixbe,

What ACME client/program are you using to request a certificate?

We changed the subscriber agreement yesterday and your client has a bug (It probably hardcodes the old URL).

Some clients (Dehydrated, simp_le) have fixed the bug and you may be able to update your client to the newest version to fix this.

I’m using the DirectAdmin control pane on my CentOS box with Let’s Encrypt plugin on it.

Looking into DirectAdmin forums then, will probably just have to run a buildupdate then.

Thought it was a problem on the Let’s Encrypt side of things.

Jeroen

1 Like

Aha. You'll have to open a support ticket with DirectAdmin and the folks responsible for maintaining the Let's Encrypt plugin.

In the short-term they will need to update the subscriber agreement URL to the current value.

In the future I'd recommend that they investigate updating their ACME client code to not require hardcoding the URL. The protocol itself provides two ways for clients to learn the current URL and using one of these instead of hardcoding will prevent this bug from happening again in the future.

Best of luck,

1 Like

Thanks for your prompt responses.
Will close this here.

Jeroen

Happy to help! Have a great day.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.