Public | Automated Build

Last pushed: a year ago
Short Description
A simple key-csr-crt manager for Let's Encrypt. That doesn't depend on the Certbot.
Full Description

docker-certs-manager

A simple key-csr-crt manager for Let's Encrypt, that uses the ACME protocol to generate the certificates. Internally uses the python script acme-tiny.

Why it's useful?

It helps in container environments like CoreOS. Centralizes the creation, distribution and renewal of domain certificates. Also, with a cron or systemd-timer, you could configure auto-renewal certificates for your domains.

How does it distribute the files?

All files will be stored in a main directory of your choise (for this tutorial, we'll use /data/letsencrypt), and categorized in the subfolders:

  • /data/letsencrypt/key/account.key --> This is fixed and it will store the Let's encrypt account key.
  • /data/letsencrypt/key/<domain>/<domain>.key --> For storing keys.
  • /data/letsencrypt/csr/<domain>/<domain>.csr --> For storing certificate signing requests.
  • /data/letsencrypt/crt/<domain>/<domain>.crt --> For storing certificates.
  • /data/letsencrypt/challenges/<domain>/ --> For storing challenges directories.

For example, for the domain example.com, you'll have:

/data/letsencrypt/key/account.key
/data/letsencrypt/key/example.com/example.com.key
/data/letsencrypt/csr/example.com/example.com.csr
/data/letsencrypt/crt/example.com/example.com.crt
/data/letsencrypt/challenges/example.com/

How it works, and what's the "challenges" directory?

After generating the domain key, and certificate signing request file, you are searching for generating the domain certificate, but first, you must prove you own the domain you want a certificate for. Let's Encrypt requires you host some challenge files on them (Particularly under http://<domain>/.well-known/acme-challenge/).

But, how do you get those challente files? Don't worry, the script acme-tiny will write them for you, connect to Let's Encrypt to validate you own the domain, and finally will generate your certificate. Let's Encrypt will perform a plain HTTP request to port 80 on your server, so you must serve the challenge files via HTTP (a redirect to HTTPS is fine too).

How to use it?

  1. Pull the image from the hub:

     $ docker pull facundovictor/docker-certs-manager
    
  2. Create the folder where you'll store the files (this will be mapped to /var/letsencrypt/ folder inside the container):

     mkdir -p /data/letsencrypt/
    
  3. Generate your Let's Encrypt account key:

     docker run --rm -v /data/letsencrypt/:/var/letsencrypt/ facundovictor/docker-certs-manager generate_key account
    
  4. Generate your domain private key (For the sake of explain it, we'll continue using the domain example.com):

     docker run --rm -v /data/letsencrypt/:/var/letsencrypt/ facundovictor/docker-certs-manager generate_key domain example.com
    
  5. Generate your domain CSR (certificate signing request): The ACME protocol (what Let's Encrypt uses) requires a CSR file to be submitted to it, even for renewals. You can use the same CSR for multiple renewals. NOTE: you can't use your account private key as your domain private key!

     docker run --rm -v /data/letsencrypt/:/var/letsencrypt/ facundovictor/docker-certs-manager generate_csr domain example.com
    
  6. Make your website host challenge files: You must prove you own the domains you want a certificate for, so Let's Encrypt will perform a plain HTTP request to port 80 on your server, and will ask for the challenge files. This script will generate and write those files, so all you need to do is make sure that the /data/letsencrypt/challenges/<your-domain>/ folder is served under the /.well-known/acme-challenge/ url path.

     #make some challenge folder (modify to suit your needs)
     mkdir -p /var/www/challenges/
     #example for nginx
     server {
         listen 80;
         server_name yoursite.com www.yoursite.com;
    
         location /.well-known/acme-challenge/ {
             alias /var/www/challenges/;
             try_files $uri =404;
         }
    
         ...the rest of your config
     }
    

    NOTE: Let's Encrypt will perform a plain HTTP request to port 80 on your server, so you must serve the challenge files via HTTP (a redirect to HTTPS is fine too).

  7. Generate your domain certificate:

     docker run --rm -v /data/letsencrypt/:/var/letsencrypt/ facundovictor/docker-certs-manager generate_crt domain example.com
    

Configure auto-renewal

You don't need anything else to renew the certificate, just repeating the step number 7 should do the work. Thus, for configure the renewal every 3 months, a cronjob is enough:

```sh
00 00 00 */3 *      /path/to/docker run --rm -v /data/letsencrypt/:/var/letsencrypt/ facundovictor/docker-certs-manager generate_crt domain example.com
```

Or if you prefer to set up a systemd timer, then add the following files in /etc/systemd/system/ or /usr/lib/systemd/system:

**example.com.renewal.service**

```sh
[Unit]
Description=cxample.com renewal

[Service]
Type=simple
ExecStart=/path/to/docker run --rm -v /data/letsencrypt/:/var/letsencrypt/ facundovictor/docker-certs-manager generate_crt domain example.com
```

**example.com.renewal.timer**

```sh
[Unit]
Description=cxample.com renewal every 3 months

[Timer]
# Time to wait after booting before we run first time
OnBootSec=10min
OnCalendar=* *-0/3-1 00:00:00
Unit=example.com.renewal.service
```

And finally enable the timer:

```sh
systemctl enable example.com.renewal.timer
```
Docker Pull Command
Owner
facundovictor
Source Repository

Comments (0)