Originally created by @alexzorin on GitHub (Sep 10, 2019).
When you dehydrated --register a new ACMEv2 account, dehydrated correctly extracts the Account URL from the Location header in the registration response:
However, on subsequent request (e.g. in dehydrated -c), dehydrated does not use that ACCOUNT_URL, and instead assumes that the account URL is constructed from the newAccount resource in the directory:
In the case when you run against Pebble, this leads to a JWS error, because
the real account URL is e.g. https://localhost:14000/my-account/8, whereas
the account URL submitted by dehydrated is https://localhost:14000/sign-me-up/8.
Originally created by @alexzorin on GitHub (Sep 10, 2019).
When you `dehydrated --register` a new ACMEv2 account, dehydrated correctly extracts the Account URL from the `Location` header in the registration response:
https://github.com/lukas2511/dehydrated/blob/018254974cb6cbf93ba9249b06b2d923e37a9e88/dehydrated#L414
However, on subsequent request (e.g. in `dehydrated -c`), dehydrated does not use that `ACCOUNT_URL`, and instead assumes that the account URL is constructed from the `newAccount` resource in the directory:
https://github.com/lukas2511/dehydrated/blob/018254974cb6cbf93ba9249b06b2d923e37a9e88/dehydrated#L421
In the case when you run against [Pebble](https://github.com/letsencrypt/pebble), this leads to a JWS error, because
- the real account URL is e.g. `https://localhost:14000/my-account/8`, whereas
- the account URL submitted by dehydrated is `https://localhost:14000/sign-me-up/8`.
adam
added the bug label 2025-12-29 01:25:00 +01:00
Hi @alexzorin I was also trying to run against Pebble and found your issues, feel free to give #727 a test if you have some time 😊
@Rogdham commented on GitHub (Mar 30, 2020):
Hi @alexzorin I was also trying to run against Pebble and found your issues, feel free to give #727 a test if you have some time :blush:
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @alexzorin on GitHub (Sep 10, 2019).
When you
dehydrated --registera new ACMEv2 account, dehydrated correctly extracts the Account URL from theLocationheader in the registration response:https://github.com/lukas2511/dehydrated/blob/018254974cb6cbf93ba9249b06b2d923e37a9e88/dehydrated#L414
However, on subsequent request (e.g. in
dehydrated -c), dehydrated does not use thatACCOUNT_URL, and instead assumes that the account URL is constructed from thenewAccountresource in the directory:https://github.com/lukas2511/dehydrated/blob/018254974cb6cbf93ba9249b06b2d923e37a9e88/dehydrated#L421
In the case when you run against Pebble, this leads to a JWS error, because
https://localhost:14000/my-account/8, whereashttps://localhost:14000/sign-me-up/8.@Rogdham commented on GitHub (Mar 30, 2020):
Hi @alexzorin I was also trying to run against Pebble and found your issues, feel free to give #727 a test if you have some time 😊
@lukas2511 commented on GitHub (Apr 2, 2020):
Replaced by #727, will be fixed soon! Thanks!