Adding auto certificate renewal to automatic letsencrypt certificate section of virtualmin config

Submitted by tripkin on Fri, 06/17/2016 - 03:49

Hi, I have enabled automatic Letsencrypt certificates on domain creation. What I would like is to be able to set automatic renewal period, for eg. 2 months. Right now, after generating the cert, I still have to go and reapply for a cert in order to get the two month auto renewal to be set.

Also, in the Manage SSL certificate area, in the Letsencrypt section, can we have a save button to save settings without having to request a certificate?

Thanks for your help!

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Fri, 06/17/2016 - 20:37

Do you mean turning on automatic renewal, but without requesting a new cert at the same time?

Submitted by tripkin on Fri, 06/17/2016 - 20:41

Precisely. As well as being able to choose auto renewal and the number of months when you choose to get a letsencrypt cert when creating a domain in the "System Settings:Virtualmin Configuration:Request Let's Encrypt certificate at domain creation time ?" area.

Submitted by JamieCameron on Sat, 06/18/2016 - 00:43

Good idea - this will be possible in the next Virtualmin release.

Submitted by tripkin on Sat, 06/18/2016 - 02:02

Sweet thanks. I recently had another idea as well, is it possible to get a list of all the domains with certs, issuers, and expiry dates? If it can even be done...

Submitted by JamieCameron on Sat, 06/18/2016 - 17:33

You can use the virtualmin get-ssl API command to display information about a domain's cert. You'd need to write a shell script that calls it in a loop which iterates through all the domain names output by virtualmin list-domains --with-feature ssl --name-only

Submitted by tripkin on Sat, 06/18/2016 - 17:37

Thanks Jamie. I will give it try and see what kind of mess I can make of things. [NOTE: I am really good at that, but getting better and cleaning the messes up...]

Submitted by JamieCameron on Sat, 07/02/2016 - 19:31

A proper UI for this has been implemented, for inclusion in the next release.

Submitted by JamieCameron on Sat, 07/02/2016 - 19:31

Status: Active » Fixed

Submitted by tripkin on Sat, 07/02/2016 - 19:41

Thanks again, Jamie! You guys are awesome!! We can close this now if it has not already been done.

Submitted by tripkin on Sat, 07/02/2016 - 19:42

Status: Fixed » Closed (fixed)