Setup a Let's encrypt certificate with Traefik

May 23, 2018
Docker traefik

Setup a Let’s Encrypt certificate with Traefik

In this post, i will explain you how to setup your first Let’s Encrypt certificate with Traefik. You need to know a little about Traefik. You can read my first post about it.

Basic setup

For this test, you need to have a machine with port 80 and 443 reachable from the internet.

For the curious, you can find more informations about Let’s Encrypt here.

Now launch traefik:

docker run --rm --name traefik --network test --publish 80:80 --publish 443:443 --publish 8080:8080 \
       -v /var/run/docker.sock:/var/run/docker.sock \
       traefik:1.6-alpine \
       --entryPoints="Name:http Address::80" \
       --entryPoints="Name:https Address::443 TLS"  \
       --api --docker --docker.endpoint="unix:///var/run/docker.sock" --loglevel=debug \
       --acme=true --acme.entrypoint=https --acme.httpchallenge --acme.httpchallenge.entrypoint=http \""""

I will now explain the new options used here :

WARNING : i will explain why you will need to change later.

Wait a few seconds and you should see something like this in the logs:

time="2018-05-23T08:59:29Z" level=debug msg="Building ACME client..."
time="2018-05-23T08:59:29Z" level=debug msg=""
time="2018-05-23T08:59:29Z" level=info msg=Register...
time="2018-05-23T08:59:32Z" level=debug msg="Using HTTP Challenge provider."
time="2018-05-23T08:59:33Z" level=debug msg="Unable to split host and port: address missing port in address. Fallback to request host."
time="2018-05-23T08:59:33Z" level=debug msg="Looking for an existing ACME challenge for token e-d4CY0MHvtZkZT0VSR7DSEF-Kz2bgrXmBGEneTFjJY0..."
time="2018-05-23T08:59:38Z" level=debug msg="Challenge CleanUp for domain"
time="2018-05-23T09:00:18Z" level=debug msg="Certificates obtained for domains []"
time="2018-05-23T09:00:18Z" level=debug msg="Configuration received from provider ACME: ....

Now your certifcate is generated and you can access the URL with https.

Tune your traefik setup

The main disadvantage of the first setup is the If the certificate is stored on the container itself, you will have to regenerate it each time the container will restart.

It’s best to store it (them) on a docker volume and to mount this volume on the container.

Here are the small optimizations we can do :

Hardening the configuration (by frontend)

By default, we will obtain a grade A with Traefik on SSL Labs. We can obtain a grade A+ by adding more options.

These options are setup by frontend :

docker run --rm --network test --label traefik.backend=nginx1 --label traefik.port=80 \
           --label traefik.frontend.rule="" \
           --label traefik.frontend.entryPoints=https \
           --label traefik.frontend.headers.forceSTSHeader=true \
           --label traefik.frontend.headers.STSSeconds=315360000 \
           --label traefik.frontend.headers.STSIncludeSubdomains=true \
           --label traefik.frontend.headers.STSPreload=true \

The explanations :

You can find more informations about HTTP Strict Transport Security here

Enjoy 😏

Use constraints with Swarm

September 4, 2018

Traefik for the beginners

May 4, 2018
Docker traefik

Docker LEMP stack: get your logs with rsyslog

February 21, 2018