Submitted by stretch on Tue, 01/24/2017 - 11:58
Hi, Today I have noticed that lets encrypt certificates for my domains weren't renewed automatically, I tried to request the renewal manually but it didn't work as well, when I press "Only update renewal" button it just loads the "Current certificate" page without renewing it. "Request certficate" works well. Renewal doesn't work both for expired and for still current certificates.
I checked for a cron job responsible for renewing and have found only /etc/webmin/package-updates/update.pl daily cron job. My Webmin version is 1.831 and Virtualmin version is 5.05.
Status:
Closed (fixed)
Comments
Submitted by stretch on Tue, 01/24/2017 - 12:17 Comment #1
Submitted by JamieCameron on Wed, 01/25/2017 - 01:56 Comment #2
If you renewal manually, do you get an error message? And if so, what is it?
Submitted by stretch on Wed, 01/25/2017 - 06:31 Comment #3
No error message at all, I tried doing this on two different virtualmin installations.
->I tried to request the renewal manually but it didn't work as well, when I press "Only update renewal" button it just loads the "Current certificate" page without renewing it.
Submitted by JamieCameron on Wed, 01/25/2017 - 23:58 Comment #4
The "Only update renewal" button just updates the number of months before automatic renewal will happen. What if you click the other button, to re-request a cert?
Submitted by stretch on Thu, 01/26/2017 - 01:54 Comment #5
Certificate re-request works. But why didn't automatic renewal happen?
Submitted by clockwork on Thu, 01/26/2017 - 06:32 Comment #6
You sure that you don't have manual renewal set ?
Submitted by stretch on Thu, 01/26/2017 - 13:38 Comment #7
I have "Months between automatic renewal" set to 1.
Submitted by JamieCameron on Thu, 01/26/2017 - 19:13 Comment #8
Hmmm ... did you get an email to
root
about automatic renewal failing?Submitted by stretch on Sat, 01/28/2017 - 08:35 Comment #9
No, I cannot find error message in logs as well
Submitted by JamieCameron on Mon, 01/30/2017 - 01:43 Comment #10
What if you go to Webmin -> Webmin Configuration -> Webmin Scheduled Functions , check the box next to "renew_letsencrypt_cert" and click Run Selected Functions Now?
Submitted by stretch on Tue, 01/31/2017 - 06:20 Comment #11
Here's it, there's no such scheduled task! Why hasn't it been created and how can I create it?
Submitted by JamieCameron on Tue, 01/31/2017 - 15:27 Comment #12
On which page did you originally setup Let's Encrypt and automatic renewal?
Submitted by stretch on Thu, 02/02/2017 - 07:07 Comment #13
On the "Manage SSL Certificate"->"Let's encrypt" page. As I remember it has been rolled out with one of the updates last spring.
Submitted by stretch on Fri, 02/03/2017 - 06:24 Comment #14
Any ideas how can I assist in resolving the issue? When is the lets encrypt certificate update scheduled task created?
Submitted by gnilebein on Fri, 02/03/2017 - 09:58 Comment #15
I have the same issue. The scheduled Task is also missing in my setup:
Ubuntu 16.04 with nginx.
Submitted by uinfor on Mon, 02/06/2017 - 03:43 Pro Licensee Comment #16
I not have too this scheduled task, and fresclam not have scheduled task too
Every 3600 seconds System Status scheduled_collect_system_info
Every 300 seconds Virtualmin Virtual Servers run_cron_script backup.pl --id 14835470861061 Every day at 7:00
Submitted by JamieCameron on Mon, 02/06/2017 - 19:24 Comment #17
Note that if you setup Let's Encrypt renewal in Virtualmin (at Server Configuration -> Manage SSL Certificate -> Let's Encrypt), then it is the
collectinfo.pl
script that will do the renewal.Submitted by stretch on Wed, 02/08/2017 - 07:36 Comment #18
@JamieCameron Any hope that auto update will be fixed? I've found another issue https://www.virtualmin.com/node/45505 where this is described, and there you have said that it will be fixed in the 5.05 release.
Submitted by stretch on Thu, 03/02/2017 - 02:46 Comment #19
domains are still not renewed automatically in nginx setup(even with fix on line 2148 which fixes only manual renewal)
Submitted by JamieCameron on Thu, 03/02/2017 - 22:26 Comment #20
Have you upgraded to 5.06-2 ? Because that contains further fixes..
Submitted by stretch on Sun, 09/24/2017 - 10:54 Comment #21