This module installs the Let's Encrypt client from source and allows you to request certificates.


This module requires Puppet >= 3.4. and is currently only written to work on Debian and RedHat based operating systems, although it may work on others.


On EL (Red Hat, CentOS etc.) systems, the EPEL repository needs to be enabled for the Let's Encrypt client package.

The module can integrate with stahnma/epel to set up the repo by setting the configure_epel parameter to true and installing the module.


To install the Let's Encrypt client with the default configuration settings you must provide your email address to register with the Let's Encrypt servers:

class { ::letsencrypt:
  email => '[email protected]',

If using EL7 without EPEL-preconfigured, add configure_epel:

class { ::letsencrypt:
  configure_epel => true,
  email          => '[email protected]',

This will install the Let's Encrypt client and its dependencies, agree to the Terms of Service, initialize the client, and install a configuration file for the client.

Alternatively, you can specify your email address in the $config hash:

class { ::letsencrypt:
  config => {
    email  => '[email protected]',
    server => '',

If you don't wish to provide your email address, you can set the unsafe_registration parameter to true (this is not recommended):

class { ::letsencrypt:
  unsafe_registration => true,

To request a certificate for using the certonly installer and the standalone authenticator:

letsencrypt::certonly { '': }

To request a certificate for and with the certonly installer and the apache authenticator:

letsencrypt::certonly { 'foo':
  domains => ['', ''],
  plugin  => 'apache',

If you need to pass a command line flag to the letsencrypt-auto command that is not supported natively by this module, you can use the additional_args parameter to pass those arguments:

letsencrypt::certonly { 'foo':
  domains         => ['', ''],
  plugin          => 'apache',
  additional_args => ['--foo bar', '--baz quuz'],


  1. Fork it

  2. Create a feature branch

  3. Write a failing test

  4. Write the code to make that test pass

  5. Refactor the code

  6. Submit a pull request

We politely request (demand) tests for all new features. Pull requests that contain new features without a test will not be considered. If you need help, just ask!