I have Let’s Encrypt accounts created with other software, and now I want to use one of them with Certbot.
1 Like
Certbot doesn’t have functionality to do this out of the box.
What you might be able to do is allow Certbot to register an account, and then replace the private_key.json
file (which is just the canonical JWK JSON representation of your account private key) and update the account URI in regr.json
.
If your existing account key is in PEM format, it’s possible to convert it into the JWK JSON format as required.
It should then begin using your account instead.
I should add that if you can, it would just be easier to use a new account. It’s no big deal to have multiple accounts. Some valid reasons where you must use the same account are:
- You have been given a rate limit exemption against your ACME account by Let’s Encrypt, or
- You intend to use the
accounturi
CAA mechanism and would have too many CAA records
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.