36

The email address used as the admin email when we started using let's encrypt needs to be modified (a former employee used his personal email address as the admin email and he is no longer with the firm). What steps need to be taken to get that modified (we can get the former employee to confirm this). We need to remove his personal email address and replace it with a new email address. This will be used for key recovery actions. In either case, I would like the former employee's personal email address to be removed. What steps do I need to take to accomplish this (if my understanding of the process is incorrect, kindly point me to the right direction). Thanks in advance.

1
  • 1
    I ended up creating a new certificate (since I was in control of the server/domain and was able to replace the existing one).
    – ali haider
    Dec 28, 2016 at 15:33

5 Answers 5

1

Because Let's Encrypt is a certificate authority, I'm guessing you want to update the data (an email) within your certificate.

If the certificate was signed, there is no way to update it. A new certificate will need to be produced.

2
  • yes, that's what I am resorting to, thanks for sharing
    – ali haider
    Jan 25, 2016 at 19:55
  • 20
    This is actually incorrect. LE doesn't add the email to the signed certificate. The registered email address is only used for expiration notifications. And it can be updated via the ACME protocol if you have the original account key. Mar 14, 2018 at 15:03
60

Use:

certbot-auto register --update-registration --email [email protected]

or

certbot register --update-registration --email [email protected]

or

certbot update_account --email [email protected]

certbot-auto or certbot will work if you have the executable under /usr/sbin. If you're unable to call certbot-auto globally, use the path to the certbot-auto file.

Source: https://letsencrypt.org/docs/expiration-emails/

3
  • Update: serverfault.com/a/901618/294929
    – uzsolt
    Apr 17, 2018 at 9:37
  • Will the second command register a new account?
    – golimar
    Dec 11, 2020 at 16:09
  • 5
    The second suggestion, certbot register --update-registration is now reported as deprecated in favour of certbot update_account Jan 28, 2021 at 22:06
14

Update based on https://letsencrypt.org/docs/expiration-emails/

certbot update_account --email [email protected]

Before This is just an update on n3rve's answer, since certbot-auto didn't work for me:

certbot register --update-registration --email [email protected]
13

There is also a contact email address stored by the python letsencrypt client under: /etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/{someKindOfHash}/regr.json

I believe that if you create multiple certs from the same letsencrypt client instance, it reuses the email address stored in regr.json, at least for expiry alert emails.

1
  • This is the more correct answer. Apr 11, 2017 at 19:05
8

According to https://letsencrypt.org/docs/expiration-emails/

certbot update_account --email [email protected]

I guess it keeps on changing

3
  • Yes, indeed it does. Documentation is an ongoing process.
    – lupo
    Aug 2, 2019 at 9:40
  • Was there not once syntax to add multiple emails? And the snap I am using has no man entry?
    – mckenzm
    Jan 9, 2023 at 22:48
  • comma delimited, link.
    – YesItsMe
    Jan 11, 2023 at 4:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .