Let’s Encrypt ALL THE THINGS


Got my first domain using a cert from Let’s Encrypt in under ~10 minutes, including setting up Let’s Encrypt itself. Yes, this is rather game changing.

Now to write ansible playbooks around it, and figure out how to get it working for proxied domains automatically.

Notes from using Let’s Encrypt:

  1. Docs really need a quickstart guide
  2. …no RPM? Shame! (copr doesn’t really count)
  3. git clone? Better than curling a shell script, I suppose
  4. Oh wait, letsencrypt-auto runs & installs stuff.
  5. What is the difference between letsencrypt and letsencrypt-auto? https://letsencrypt.readthedocs.org/en/latest/using.html#webroot uses plain letsencrypt, letsencrypt-auto worked as well though
  6.  ./letsencrypt-auto certonly –webroot -w /var/www/<domain>/ -d <domain> is the command. Tack on however many -d <domains> for the same webroot
  7. auth directory starts with a . – nginx config had to be changed to allow . directories to be read. Follow least principal and do location ^~ /.well-known/ {allow all;}
  8. It generates all certs & chains. I use nginx so fullchain.pem became my .crt file, and privkey became my .key file (I didn’t use .pem extensions when creating my own keys originally)
  9. nginx -t double checks that the private key matches the public key (don’t do this by steps)

 

 

,

  1. No comments yet.
(will not be published)