Originally created by @dave559 on GitHub (Mar 18, 2020).
Is it possible to use dehydrated to register with LetsEncrypt with an email address (rather than just anonymously)?
LetsEncrypt will send warning emails to accounts registered with an email address if, for some reason, a cert hasn't been renewed close to the expiry date, which could be a useful feature to make use of in the event that something goes wrong with the automated processes on one's webserver.
I can see that there is an --account option, but I can't see any instructions about how to use it?
Originally created by @dave559 on GitHub (Mar 18, 2020).
Is it possible to use dehydrated to register with LetsEncrypt with an email address (rather than just anonymously)?
LetsEncrypt will send warning emails to accounts registered with an email address if, for some reason, a cert hasn't been renewed close to the expiry date, which could be a useful feature to make use of in the event that something goes wrong with the automated processes on one's webserver.
I can see that there is an `--account` option, but I can't see any instructions about how to use it?
The --account option updates the account information Let's Encrypt has from what is specified in the config file, you can specify the email address in the config file.
The config file is simply a file named "config" created from docs/examples/config in the same directory as the dehydrated script.
@jobe1986 commented on GitHub (Mar 18, 2020):
The --account option updates the account information Let's Encrypt has from what is specified in the config file, you can specify the email address in the config file.
The config file is simply a file named "config" created from docs/examples/config in the same directory as the dehydrated script.
Just to elaborate, there is a CONTACT_EMAIL= setting (which is unset by default) in the config file, which the site admin can uncomment and then append the appropriate email address to, and then run dehydrated --account for that setting to be updated.
It is also possible to add this setting to a local config file in the conf.d folder, which may be an easier way to do this for our automated server configuration setup.
@dave559 commented on GitHub (Apr 1, 2020):
Thanks, jobe1986.
Just to elaborate, there is a `CONTACT_EMAIL=` setting (which is unset by default) in the `config` file, which the site admin can uncomment and then append the appropriate email address to, and then run `dehydrated --account` for that setting to be updated.
It is also possible to add this setting to a local config file in the `conf.d` folder, which may be an easier way to do this for our automated server configuration setup.
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 @dave559 on GitHub (Mar 18, 2020).
Is it possible to use dehydrated to register with LetsEncrypt with an email address (rather than just anonymously)?
LetsEncrypt will send warning emails to accounts registered with an email address if, for some reason, a cert hasn't been renewed close to the expiry date, which could be a useful feature to make use of in the event that something goes wrong with the automated processes on one's webserver.
I can see that there is an
--accountoption, but I can't see any instructions about how to use it?@jobe1986 commented on GitHub (Mar 18, 2020):
The --account option updates the account information Let's Encrypt has from what is specified in the config file, you can specify the email address in the config file.
The config file is simply a file named "config" created from docs/examples/config in the same directory as the dehydrated script.
@dave559 commented on GitHub (Apr 1, 2020):
Thanks, jobe1986.
Just to elaborate, there is a
CONTACT_EMAIL=setting (which is unset by default) in theconfigfile, which the site admin can uncomment and then append the appropriate email address to, and then rundehydrated --accountfor that setting to be updated.It is also possible to add this setting to a local config file in the
conf.dfolder, which may be an easier way to do this for our automated server configuration setup.