Public | Automated Build

Last pushed: a month ago
Short Description
Cronified LetsEncrypt container.
Full Description


Create and automatically renew website SSL certificates using the letsencrypt free certificate authority, and its client certbot.

This image will renew your certificates every 2 months, and place the lastest ones in the /certs folder in the container, and in the ./certs folder on the host.



In docker-compose.yml, change the environment variables:

  • WEBROOT: set this variable to the webroot path if you want to use the webroot plugin. Leave to use the standalone webserver.
  • DOMAINS: a space separated list of domains for which you want to generate certificates.
  • EMAIL: where you will receive updates from letsencrypt.
  • CONCAT: true or false on whether you want to concatenate the certificate's full chain with the private key (required for e.g. haproxy), or keep the two files separate (required for e.g. nginx or apache).


Using the automated image

docker run --name certbot -v `pwd`/certs:/certs --restart always -e "" -e "" -e "CONCAT=true" -e "WEBROOT=" henridwyer/docker-letsencrypt-cron

Building the image

The easiest way to build the image yourself is to use the provided docker-compose file.

docker-compose up -d

The first time you start it up, you may want to run the certificate generation script immediately:

docker exec certbot ash -c "/scripts/"

At 3AM, on the 1st of every odd month, a cron job will start the script, renewing your certificates.

ACME Validation challenge

To authenticate the certificates, the you need to pass the ACME validation challenge. This requires requests made on port 80 to to be forwarded to this container.

The recommended way to use this image is to set up your reverse proxy to automatically forward requests for the ACME validation challenges to this container.

Haproxy example

If you use a haproxy reverse proxy, you can add the following to your configuration file in order to pass the ACME challenge.

frontend http
  bind *:80
  acl letsencrypt_check path_beg /.well-known

  use_backend certbot if letsencrypt_check

backend certbot
  server certbot certbot:80 maxconn 32

Nginx example

If you use nginx as a reverse proxy, you can add the following to your configuration file in order to pass the ACME challenge.

upstream certbot_upstream{
  server certbot:80;

server {
  listen              80;
  location '/.well-known/acme-challenge' {
    default_type "text/plain";
    proxy_pass http://certbot_upstream;

More information

Find out more about letsencrypt:

Certbot github:



  • Add support for webroot mode.
  • Run certbot once with all domains.


  • Upgraded to use certbot client
  • Changed image to use alpine linux


  • Initial release
Docker Pull Command