Ansible Role - Certbot (for Let's Encrypt)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Dieter Provoost ce3a65be99 allow cron renew arguments to be configurable 7 years ago
defaults PR #19 follow-up: Docs fixes and reordering defaults. 8 years ago
meta package module requires Ansible >= 2.0 8 years ago
tasks allow cron renew arguments to be configurable 7 years ago
tests Merge pull request #19 from exploide/package-install 8 years ago
vars allow cron renew arguments to be configurable 7 years ago
.gitignore Switch to more efficient and compact test setup. 8 years ago
.travis.yml Merge branch 'master' into package-install 8 years ago
LICENSE Add a LICENSE file for MIT license. [ci skip] 8 years ago
README.md Issue #6: Add more documentation around automatically generating certs. 7 years ago

README.md

Ansible Role: Certbot (for Let's Encrypt)

Build Status

Installs and configures Certbot (for Let's Encrypt).

Requirements

If installing from source, Git is required. You can install Git using the geerlingguy.git role.

Role Variables

The variable certbot_install_from_source controls whether to install Certbot from Git or package management. The latter is the default, so the variable defaults to no.

certbot_auto_renew: true
certbot_auto_renew_user: "{{ ansible_user }}"
certbot_auto_renew_hour: 3
certbot_auto_renew_minute: 30

By default, this role configures a cron job to run under the provided user account at the given hour and minute, every day. The defaults run certbot renew (or certbot-auto renew) via cron every day at 03:30:00 by the user you use in your Ansible playbook. It's preferred that you set a custom user/hour/minute so the renewal is during a low-traffic period and done by a non-root user account.

Source Installation from Git

You can install Certbot from it's Git source repository if desired. This might be useful in several cases, but especially when older distributions don't have Certbot packages available (e.g. CentOS < 7, Ubuntu < 16.10 and Debian < 8).

certbot_install_from_source: no
certbot_repo: https://github.com/certbot/certbot.git
certbot_version: master
certbot_keep_updated: yes

Certbot Git repository options. To install from source, set certbot_install_from_source to yes. This clones the configured certbot_repo, respecting the certbot_version setting. If certbot_keep_updated is set to yes, the repository is updated every time this role runs.

certbot_dir: /opt/certbot

The directory inside which Certbot will be cloned.

Dependencies

None.

Example Playbook

- hosts: servers

  vars:
    certbot_auto_renew_user: your_username_here
    certbot_auto_renew_minute: 20
    certbot_auto_renew_hour: 5

  roles:
    - geerlingguy.certbot

Creating certificates with certbot

After installation, you can create certificates using the certbot (or certbot-auto) script (use letsencrypt on Ubuntu 16.04, or use /opt/certbot/certbot-auto if installing from source/Git. Here are some example commands to configure certificates with Certbot:

# Automatically add certs for all Apache virtualhosts (use with caution!).
certbot --apache

# Generate certs, but don't modify Apache configuration (safer).
certbot --apache certonly

If you want to fully automate the process of adding a new certificate, you can do so using the command line options to register, accept the terms of service, and then generate a cert using the standalone server:

  1. Make sure any services listening on port 80 (Apache, Nginx, Varnish, etc.) are stopped.
  2. Register with something like certbot register --agree-tos --email [your-email@example.com] - Note: You won't need to do this step in the future, when generating additional certs on the same server.
  3. Generate a cert for a domain whose DNS points to this server: certbot certonly --noninteractive --standalone -d example.com -d www.example.com
  4. Re-start whatever was listening on port 80 before.
  5. Update your webserver's virtualhost TLS configuration to point at the new certificate (fullchain.pem) and private key (privkey.pem) Certbot just generated for the domain you passed in the certbot command.
  6. Restart your webserver so it uses the new HTTPS virtualhost configuration.

Certbot certificate auto-renewal

By default, this role adds a cron job that will renew all installed certificates once per day at the hour and minute of your choosing.

You can test the auto-renewal (without actually renewing the cert) with the command:

/opt/certbot/certbot-auto renew --dry-run

See full documentation and options on the Certbot website.

License

MIT / BSD

Author Information

This role was created in 2016 by Jeff Geerling, author of Ansible for DevOps.