Submitted by yngens on Wed, 09/06/2017 - 04:12
Usually, when SSL is enabled then the system generates self-signed certificate. And that's good because not all the domains are ready to pass Let's Encrypt verification. However, in our use case we need to generate Let's Encrypt as soon as SSL is enabled. I wonder if there is a way to automotize this. If post creation script needs to be used then what is the Virtualmin CLI command to generate Let's Encrypt? Thanks!
Status:
Closed (works as designed)
Comments
Submitted by andreychek on Wed, 09/06/2017 - 09:57 Comment #1
Howdy -- there isn't a way to do that when SSL is enabled.
However, now that SSL is becoming more common, there's a feature for enabling Let's Encrypt for all domains as they are created.
That feature can be enabled in System Settings -> Virtualmin Config -> SSL Options -> "Request Let's Encrypt certificate at domain creation time?".
Submitted by yngens on Wed, 09/06/2017 - 12:00 Comment #2
That's cool. Gonna try today later and see.
Submitted by yngens on Wed, 09/06/2017 - 12:55 Comment #3
It kind of worked, but failed giving:
DNS-based validation failed : DNS zone www.sub8.domain.com does not exist on this systemWe tried to turn www. off for sub-dmains, however as described on https://www.virtualmin.com/node/53396 it is always on.
Eric,
Could you please elaborate how we could overcome this obstacle and comment something on https://www.virtualmin.com/node/53396
Submitted by yngens on Wed, 09/06/2017 - 12:56 Comment #4
The solution would be if we could make Let's Encrypt to auto-request certificates only for the subdomain itself without www.
Submitted by yngens on Wed, 09/06/2017 - 17:26 Comment #5
Since I've got satisfactory solution to the subject matter of this issue, I am closing it and going to open a new one for www. problem.
Submitted by JamieCameron on Wed, 09/06/2017 - 18:31 Comment #6
Ok, I didn't consider the case where you're requesting a cert for a sub-domain. That should be fixable though ..
Submitted by JamieCameron on Wed, 09/06/2017 - 18:45 Comment #7
This situation will be handled properly in the next Webmin release.