When I looked in list of systemd services I noticed that Cerbot was not running even if the list said it should. So should I start it? Certbot.timer was also not running but it looked like that was correct
Are you using Virtualmin to manage your certs? If so, then no, you don’t need certbot to run, as Webmin scheduled jobs handles it. And, in fact, if you try to use certbot directly to mess about with the same certs, you’ll break the Virtualmin-managed certs, because Virtualmin keeps it synced up across a bunch of services, which certbot doesn’t do (without extra effort and configuring some hooks).
Ok Good
I use virtualmin to manage the certs on this server. I have another pure email server without any controlpanel where I use certbot directly via ssh.
Thanks
This is true; however, the upcoming Webmin release will set the --no-autorenew flag, and once the Let’s Encrypt certificate is renewed again using Virtualmin, it will technically be possible to use Certbot’s scheduled function alongside Virtualmin. Though, it’s not really necessary!
To be clear, after the Webmin 2.300 release, it will technically be possible to use Let’s Encrypt renewals with Virtualmin alongside certbot.timer for whatever reason.