It’s great to be able to get these certificates for free and the whole process is generally very straightforward. However, since working with Let’s Encrypt certificates for the last few years I’ve noticed the same recurring questions occasionally rear their heads.
So, this is a note to “future me” (and anyone else it might help) with answers to those questions I’ve pondered in the past.
- For servers where you previously used the old, pre-Certbot Let’s Encrypt system to install SSL certs, you can just install certbot on top and it will just work. It will supersede the old certificates without conflict.
- When creating a new vhost on your Linode, DigitalOcean (or other cloud hosting platform) server, you need only add the
<VirtualHost *:80>directive. No need to add a
<VirtualHost *:443>section, nor worry about pointing to LE certificate files, nor bother writing rules to redirect http to https like I used to. When you install your secure certificate, certbot will automatically add the redirect into your original file and create an additional vhost file (with extension
-le.ssl.conf) based on the contents of your existing file but handling
and referencing all the LE SSL certificate files it installed elsewhere on the system.
- There’s no longer any need to manually add a cron job for certiticate renewal. Auto-renewal of certificates is now handled by a cron job which comes bundled with the certbot package you initially install – in my case usually a certbot ppa package for Ubuntu 16.04 or 18.04. However you won’t find that cron job in the crontab for either your limited user, nor the root user. Instead, it is installed at a lower level (
/etc/cron.d) and should just work unless you’ve done something fancy with
systemdin your system which in my case is unlikely).
- If you notice that the SSL certificate for your domain is within 30 days of expiry and hasn’t yet auto-renewed, then you know that something has gone wrong with the auto-renewal process. You can test for problems by running
sudo certbot renew --dry-run. You may find that there is, for example, a syntax error in your apache2.conf or nginx config file which needs corrected – not that this ever happened to me, of course!