Let's Encrypt certificates are not automatically renewing

I am running webmin 1.831 and webmin-virtual-server 5.07.gpl-3. I have Let's Encrypt certs on about 10 domains, and I've been monitoring these domains and the certs are not automatically renewing, even though I have "Months between automatic renewal" set to 1. If I manually renew a domain, it works just fine. The "Time since last renewal" shows 2.47 months. As the server admin, I've not received any errors, but I don't know what email address errors would be set to. Also, what is the cron that fires the Let's Encrypt renewals? I'd like to run it by hand to make sure it works and also make sure it's actually running in cron. I haven't been able to track down what process is supposed to trigger the renewals.

Thanks, Carl

Status: 
Closed (fixed)

Comments

We are just about to release Webmin 1.840, which should fix this.

Thanks! Encountered the same issue again, hope you have fixed this a last!

Hi, I have the same issue with Webmin 1.844. It did not seem to be auto renewing (my cert reached 2.37 months), so I initiated a manual renewal. I have now set it to 0.01 months to test but so far it is at 0.03 months without a renewal. I am using nginx if it helps.

Did you get any emails about failed cert renewals?

No, I do not get any emails at all.

I tried spinning a new VPS and installed virtualmin and nginx on it. Fresh install. It doesn't seem to renew certificates either.

This seems to work OK on all my test systems.

If you SSH in as root and run /etc/webmin/virtual-server/collectinfo.pl , does it output any error message?

It does not return any error message.

How do we know if the renewal script runs? Is there a server log or anything? I can't seem to find anything under crons or any system log.

I tried spinning up a new VPS, using Apache instead of nginx, and it works fine. Seems like something is wrong when using nginx?

What if you try a renewal from the command line, with a command like :

virtualmin generate-letsencrypt-cert --domain yourdomain.com

Wait, I see the bug that causes this now - it's specific to Nginx systems. It will be fixed in the 6.00 Virtualmin release.

Status: Active » Fixed
Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.