Updated Wed 14 Sep 2016 (new installation guide URL, clarify name change.)
Let’s Encrypt have updated their getting started page, but the following may help anyone trying to understand the latest changes.
If you’re installing from scratch, use Certbot (see below) and start here. You’ll get custom instructions for your operating system and web server – the client can now be installed via a package on newer systems.
The client (now at version 0.6.0) from letsencrypt-auto to Certbot – to be precise, the project/ecosystem is still called Let’s Encrypt, while Certbot is the EFF’s certificate deployment client.
You’ll find that certbot-auto (a shell script) is an exact copy of the letsencrypt-auto, so all previous commands will still work.
The git repository has also been renamed – the old one is redirected.
You can update the location of your ‘origin’ remote in .git/config
You can now renew all your certificates at once.
# to test ~/letsencrypt/certbot-auto renew --dry-run # to actually do it ~/letsencrypt/certbot-auto renew
There’s some clever stuff going on here:
- It uses all your previous settings.
- It renews any certificates that will expire within 30 days.
- Afterwards you get a list of which were renewed and which were skipped (“not due for renewal yet”)
--dry-runuse staging server, so doesn’t count towards API limits.
- “renew” is designed for unattended use.
- Remember you still need to reload apache/nginx afterwards.
Example of a cron.weekly script you could use:
#!/bin/bash /path/to/letsencrypt/certbot-auto renew service nginx reload