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, install Docker, 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/letsencrypt:latest

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

Getting the code

Please install Git and run the following commands:

git clone https://github.com/letsencrypt/letsencrypt
cd letsencrypt

Alternatively you could download the ZIP archive and extract the snapshot of our repository, but it's strongly recommended to use the above method instead.

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

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 .

Installation

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

Warning

Please do not use python setup.py install. Please do not attempt the installation commands as superuser/root and/or without Virtualenv, e.g. sudo python setup.py install, sudo pip install, sudo ./venv/bin/.... These modes of operation might corrupt your operating system and are not supported by the Let's Encrypt team!

Note

If your operating system uses SWIG 3.0.5+, you will need to run pip install -r requirements-swig-3.0.5.txt -r requirements.txt . instead. Known affected systems:

• Fedora 22
• some versions of Mac OS X

Usage

To get a new certificate run:

./venv/bin/letsencrypt auth

The letsencrypt commandline tool has a builtin help:

./venv/bin/letsencrypt --help