My domain is:
I ran this command:
certbot --agree-tos --config-dir ./certs --logs-dir ./certs/logs --work-dir ./certs update_account --email new-user@bitbrew.com
It produced this output:
Saving debug log to <path>/certs/logs/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing, once your first certificate is successfully issued, to
share your email address with the Electronic Frontier Foundation, a founding
partner of the Let's Encrypt project and the non-profit organization that
develops Certbot? We'd like to send you email about our work encrypting the web,
EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: n
Your e-mail address was updated to new-user@bitbrew.com.
OS: macOS 11.2.3
Client: certbot 1.14.0
My goal was simply to change our email address for expiration emails (the previous one was unsubscribed and the new one is of course what we need to use).
Although the output looks successful, I took a look in the directory structure and I'm concerned about the resulting changes to:
regr.json
Previously, catting this file showed:
{"body": {"key": {"n": "y1t...long key...", "e": "AQAB", "kty": "RSA"}, "contact": ["mailto:old-user@bitbrew.com"], "status": "valid"}, "uri": "https://acme-v02.api.letsencrypt.org/acme/acct/<redacted>", "terms_of_service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf"}
But after the command was run, the regr.json file only contains:
{"body": {}, "uri": "https://acme-v02.api.letsencrypt.org/acme/acct/<redacted>"}
Is this an issue that will affect our cert renewal script? Or is this simply the result of not having updated the email associated with our account for years?
Thanks in advance for any assistance.
Ben