certbot/docs/using.rst

Using the Let's Encrypt client

Quick start

Using docker you can quickly get yourself a testing cert. From the server that the domain your requesting a cert for resolves to, download docker, and issue the following command

sudo docker run -it --rm -p 443:443 --name letsencrypt \
            -v "/etc/letsencrypt:/etc/letsencrypt" \
            -v "/var/lib/letsencrypt:/var/lib/letsencrypt" \
            quay.io/letsencrypt/lets-encrypt-preview:latest

And follow the instructions. Your new cert will be available in /etc/letsencrypt/certs.

Prerequisites

The demo code is supported and known to work on Ubuntu and Debian. Therefore, prerequisites for other platforms listed below are provided mainly for the developers <hacking> reference.

In general:

• sudo is required as a suggested way of running privileged process
• SWIG is required for compiling M2Crypto
• Augeas is required for the Python bindings

Ubuntu

sudo ./bootstrap/ubuntu.sh

Debian

sudo ./bootstrap/debian.sh

For squeeze you will need to:

• Use virtualenv --no-site-packages -p python instead of -p python2.

Mac OSX

sudo ./bootstrap/mac.sh

Fedora

sudo ./bootstrap/fedora.sh

Note

Fedora 22 uses SWIG 3.0.5+, use the modified pip command for installation <new-swig>.

Centos 7

sudo ./bootstrap/centos.sh

For installation run this modified command (note the trailing backslash):

SWIG_FEATURES="-includeall -D__`uname -m`__-I/usr/include/openssl" \
./venv/bin/pip install -r requirements.txt functools32

Installation

virtualenv --no-site-packages -p python2 venv
./venv/bin/pip install -r requirements.txt

Usage

The letsencrypt commandline tool has a builtin help:

./venv/bin/letsencrypt --help