starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-11 22:30:44 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Upgrading from acme-v1 to acme-v2 causes problems #401

New Issue
Closed
opened 2025-12-29 01:24:27 +01:00 by adam · 3 comments
adam commented 2025-12-29 01:24:27 +01:00
Owner
Copy Link

Originally created by @herkyl on GitHub (Jan 23, 2019).

After updating to the latest dehydrated and setting CA to https://acme-v02.api.letsencrypt.org/directory, I'm seeing a 400 error when running --cron.

Any ideas why this is happening? Is there anything else I need to do in order to start using acme v2?

/opt/dehydrated/dehydrated --account
# INFO: Using main config file /etc/dehydrated/config
Fetching missing account information from CA...
  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-acct (Status 400)

Details:
HTTP/1.1 100 Continue
Expires: Wed, 23 Jan 2019 17:44:00 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: 134
Replay-Nonce: 4uH9rA8q6-A-Z1UqXvwGmVBdQkd8m_VhNs1zTuj3bxQ
Expires: Wed, 23 Jan 2019 17:44:01 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Wed, 23 Jan 2019 17:44:01 GMT
Connection: close

{
  "type": "urn:ietf:params:acme:error:accountDoesNotExist",
  "detail": "No account exists with the provided key",
  "status": 400
}
Originally created by @herkyl on GitHub (Jan 23, 2019). After updating to the latest dehydrated and setting `CA` to https://acme-v02.api.letsencrypt.org/directory, I'm seeing a 400 error when running `--cron`. Any ideas why this is happening? Is there anything else I need to do in order to start using acme v2? ```bash /opt/dehydrated/dehydrated --account # INFO: Using main config file /etc/dehydrated/config Fetching missing account information from CA... + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-acct (Status 400) Details: HTTP/1.1 100 Continue Expires: Wed, 23 Jan 2019 17:44:00 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: 134 Replay-Nonce: 4uH9rA8q6-A-Z1UqXvwGmVBdQkd8m_VhNs1zTuj3bxQ Expires: Wed, 23 Jan 2019 17:44:01 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Wed, 23 Jan 2019 17:44:01 GMT Connection: close { "type": "urn:ietf:params:acme:error:accountDoesNotExist", "detail": "No account exists with the provided key", "status": 400 } ```
adam closed this issue 2025-12-29 01:24:27 +01:00
adam commented 2025-12-29 01:24:28 +01:00
Author
Owner
Copy Link

@bllfr0g commented on GitHub (Jan 23, 2019):

V2 is a different endpoint so you need to register for a new account

On Jan 23, 2019, at 09:48, Serge notifications@github.com wrote:

After updating to the latest dehydrated and setting CA to https://acme-v02.api.letsencrypt.org/directory, I'm seeing a 400 error when running --cron.

Any ideas why this is happening? Is there anything else I need to do in order to start using acme v2?

/opt/dehydrated/dehydrated --account

INFO: Using main config file /etc/dehydrated/config

Fetching missing account information from CA...

Details:
HTTP/1.1 100 Continue
Expires: Wed, 23 Jan 2019 17:44:00 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: 134
Replay-Nonce: 4uH9rA8q6-A-Z1UqXvwGmVBdQkd8m_VhNs1zTuj3bxQ
Expires: Wed, 23 Jan 2019 17:44:01 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Wed, 23 Jan 2019 17:44:01 GMT
Connection: close

{
"type": "urn:ietf:params:acme:error:accountDoesNotExist",
"detail": "No account exists with the provided key",
"status": 400
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@bllfr0g commented on GitHub (Jan 23, 2019): V2 is a different endpoint so you need to register for a new account > On Jan 23, 2019, at 09:48, Serge <notifications@github.com> wrote: > > After updating to the latest dehydrated and setting CA to https://acme-v02.api.letsencrypt.org/directory, I'm seeing a 400 error when running --cron. > > Any ideas why this is happening? Is there anything else I need to do in order to start using acme v2? > > /opt/dehydrated/dehydrated --account > # INFO: Using main config file /etc/dehydrated/config > Fetching missing account information from CA... > + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-acct (Status 400) > > Details: > HTTP/1.1 100 Continue > Expires: Wed, 23 Jan 2019 17:44:00 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: 134 > Replay-Nonce: 4uH9rA8q6-A-Z1UqXvwGmVBdQkd8m_VhNs1zTuj3bxQ > Expires: Wed, 23 Jan 2019 17:44:01 GMT > Cache-Control: max-age=0, no-cache, no-store > Pragma: no-cache > Date: Wed, 23 Jan 2019 17:44:01 GMT > Connection: close > > { > "type": "urn:ietf:params:acme:error:accountDoesNotExist", > "detail": "No account exists with the provided key", > "status": 400 > } > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread.
adam commented 2025-12-29 01:24:28 +01:00
Author
Owner
Copy Link

@herkyl commented on GitHub (Jan 24, 2019):

Thanks for getting back to me @bllfr0g. Since I didn't originally set up the dehydrated script on our end I'm a bit confused. How do I register a new account? Can I do it using dehydrated itself or do I need to install certbot?

When I run dehydrated --register it prints:

/opt/dehydrated/dehydrated --register
# INFO: Using main config file /etc/dehydrated/config
+ Account already registered!

It might be referring to the v1 account though?

@herkyl commented on GitHub (Jan 24, 2019): Thanks for getting back to me @bllfr0g. Since I didn't originally set up the dehydrated script on our end I'm a bit confused. How do I register a new account? Can I do it using dehydrated itself or do I need to install certbot? When I run `dehydrated --register` it prints: ```bash /opt/dehydrated/dehydrated --register # INFO: Using main config file /etc/dehydrated/config + Account already registered! ``` It might be referring to the v1 account though?
adam commented 2025-12-29 01:24:28 +01:00
Author
Owner
Copy Link

@herkyl commented on GitHub (Jan 26, 2019):

I fixed it by manually renaming the accounts directory.

mv /etc/dehydrated/accounts /etc/dehydrated/accounts_old
/opt/dehydrated/dehydrated --register
@herkyl commented on GitHub (Jan 26, 2019): I fixed it by manually renaming the `accounts` directory. ```bash mv /etc/dehydrated/accounts /etc/dehydrated/accounts_old /opt/dehydrated/dehydrated --register ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#401
Delete Branch "%!s()"

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?