Let's Encrypt usage

Submitted by jvieille on Sat, 01/14/2017 - 01:43

Just a simple question I was not able to clarify rading all posts about that. I found extremely easy to setup a certificate to a virtual server. However, I all installation tutorials and posts were telling that I should install a "Let's Encrypt Client" on the server - which is rather tricky. I made it at some point of my testing, but the certificate seemed to work BEFORE I installed that software.

Is this needed, or shall I simply use the Let's Encrypt Tab in the virtual server certificate management and forget about that software installation? In other words, is webmin/virtualmin "Let's Encrypt ready" ?

Thanks

Status: 
Active

Comments

Submitted by andreychek on Sat, 01/14/2017 - 08:55

Howdy -- Virtualmin comes with it's own built-in Let's Encrypt client, it's not actually necessary to install any software outside of Virtualmin in order for Let's Encrypt to work.

Virtualmin at one point did require that the admin install the official Let's Encrypt client, but that's no longer necessary.

If you had any followup questions, as it looks like you're using Virtualmin GPL there, you'd want to use the Forums to get additional support. We monitor the Forums, along with lots of wonderful folks in the community. Thanks!

Submitted by hostile on Sat, 01/14/2017 - 21:42

its broken at the moment and dosent works

Submitted by JamieCameron on Sun, 01/15/2017 - 14:06

How is it broken exactly? What error message are you getting?

Submitted by jvieille on Sat, 01/21/2017 - 05:00

This is wonderful actually, so simple! I still need some more clarification that I did not get on the forum https://www.virtualmin.com/node/45527 I setup a Let's encrypt certificate for 1 month automatic renewal, but I can't find a cron job doing that. How is this renewal will be processed without a cron job ? Do I need to set this cron job? If yes, how and what is be the purpose of specifying the renewal period if it is not handled?

Thanks for help

Submitted by andreychek on Sat, 01/21/2017 - 09:19

Hi there jvieille, a Forum post like you made is the best place to ask questions for folks using Virtualmin GPL, I'll try to follow up with you there shortly! The short answer is that you do not need to do anything else for renewals to work though :-)

Submitted by JamieCameron on Wed, 02/08/2017 - 21:21

There is no separate cron job for the renewal - it is done as part of the combined Virtualmin cron.

Submitted by JamieCameron on Wed, 02/08/2017 - 21:25

Also, I tested automatic renewal in a fully updated Virtualmin 5.06 system, and it worked fine.

Submitted by stretch on Thu, 02/09/2017 - 06:33

Also, I tested automatic renewal in a fully updated Virtualmin 5.06 system, and it worked fine.

Thats great! When will it be available your repository? As my system is 5.05 and it reports that its up to date.

Submitted by JamieCameron on Thu, 02/09/2017 - 23:14

Sorry, I meant a 5.05 system. Version 5.06 is still under development.

Submitted by stretch on Fri, 02/10/2017 - 10:27

Sorry, I meant a 5.05 system. Version 5.06 is still under development. on nginx its not working, maybe you have tested it with apache?

Submitted by JamieCameron on Fri, 02/10/2017 - 17:18

On Nginx, does even requesting a Let's Encrypt cert in the first place fail? Or is the problem only with renewal?

Submitted by stretch on Sun, 02/12/2017 - 06:28

On Nginx, does even requesting a Let's Encrypt cert in the first place fail? Or is the problem only with renewal?

it works for requesting, but fails with renewal

Submitted by JamieCameron on Sun, 02/12/2017 - 18:36

We are about to release a new 5.06 version of Virtualmin that should fix this.