Let's Encrypt does not Reset Webmin certificate when other certs are reset

[l-arnold]

After the first build of Let's Encrypt (Dehydrated), (ie in the 2nd and subsequent resets) the Confconsole started script step resets Apache and Webshell Certs, but it does not reset the Webmin Cert.

You can see in the log as well. Apache, then Webshell and done. (I tried to copy the screen output but missed)

It would be helpful to also reset the Webmin certificate.

(Specifically here with TKL 17.1 Odoo 14 appliance.

[JedMeister]

Hi @l-arnold - Not saying that you are wrong, but I don't understand how this could be?! I say that because by default Webmin (via stunnel), Webshell (also via stunnel) and Apache literally use the exact same certificate! I.e they all use /etc/ssl/private/cert.pem.

I forget where the output goes by default, but there should be a log file noting what happens. It'd be great if you could find that and share it with me.

[JedMeister]

Pondering this a little more, the only other thing that occurs to me is perhaps the stunnel4@webmin.service isn't being restarted properly? Could you please try running this and see if it resolves the issue you're hitting:

systemctl restart stunnel4@webmin.service

[l-arnold]

Hi @JedMeister ,
I will test that. My current "Me thinks" that some builds have it working, while others do not...
I was working on an AWS AMI the other day, but honestly I need to find the machine where this was occurring.
Seemed to have worked today however on some other builds.

And, come to think of it. If a full system restart sets it in place, that would emulate your stunnel14@webmin.service restart, which might explain why it seemed things were working now... hmm

I'll try to report back soon.

[l-arnold]

Confirming this again. Very strange the cert that Webmin is presenting... BUT, I go back to your presumption just above:

       systemctl restart stunnel4@webmin.service

and Viola. Webmin is using the correct Cert, as the rest of the system is using.
Definitely that code should go into the Let's Encrypt Update process. Happens pretty frequently when you are moving sites around.

Thank you for this Jeremy (delayed though my thank you may be!)