How to update my "Let's Encrypt Wildcard SSL Certificat" AUTOMATICALLY when it expired?

| OS type and version | Ubuntu 20.0.4 |
| Virtualmin version | 7.9.0 |


After some months, I noticed that Let’s Encrypt Wildcard SSL Certificat is always expired.

Is there any way to make it updated automatically without never expired ???

Please help me to set updating of my Let’s Encrypt Wildcard SSL Certificat AUTOMATICALLY instead of continuing to do it manually.
Thanks in advance.

If you created it in Virtualmin, it automatically renews, as long as you let it do so.

That, of course, assumes Virtualmin is managing your DNS. If Virtualmin is not managing your DNS, Virtualmin cannot request/renew wildcard certificates, and you have to do it via certbot manually and you can’t do it automatically (because there’s a dance with DNS that has to be done to prove you own the whole zone).

Also, I recommend you not use wildcard certs, for this and several other reasons.

But how to let Virtualmin manage my DNS exactly Because I always do it manually with certbot command in my Root Terminal (Ubuntu) ???

Or how to configure Virtualmin so that it manage my DNS and renew automatically Wilcard SSL Certificates from now on ???

Create some resolvable nameserver entries that point to you server. Then at you domain supplier change the name servers to the name servers you have created but the question is why do you need a wild card certificate ? If you use virtualmin to manage all your domains/subdomains virtualmin will obtain certificates for each domain/subdomain so you shouldn’t need a wild card certificate

There’s not really a “how” related to Virtualmin, you just turn on the DNS feature, and Virtualmin creates the necessary records in the local BIND instance (and the secondary, assuming you’ve set one up according to our documentation). Making Virtualmin manage DNS couldn’t be any simpler…but, you also have to delegate name service for your zones to the Virtualmin server and its secondary via glue records.

And, that’s the part that most people have trouble with, as most people never take the time to learn how DNS works at a basic level. We have no control over this and we can’t tell you how to do it because it is different for every registrar. Even the terminology they use varies a bit. Some call the glue records “name servers”. Some allow you to spring a zone into existence from nothing by filling in both the name and IP addresses of your name servers. Others require you to already have name servers that resolve on the internet, so it takes a couple of steps to delegate to your name servers. You need to read your registrars documentation about delegating name service to other servers.

Anyway, the DNS feature in Virtualmin is on by default, all you need to do is setup a secondary DNS server and point the glue records to your Virtualmin server and the secondary. (But, you should turn it off if you are not hosting DNS locally, and then Virtualmin will provide a Suggested DNS Records page for you.)

I recommend you stop using wildcard certs if this is the only reason you want to host your own DNS. Just request certs for every name you want to use and forget about this wildcard nonsense.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.