DNS-01
Host Config: docker-traefik2-acme-host
· ☕ 1 min read · ✍️ Mark A. McFate
This post is celebrating the completion (really, is anything ever complete?) of a new server/host/stack deployment project: docker-traefik2-acme-host. In order to make this post really easy to read, I’m going to wrap it up in one bullet… README.md And that’s a wrap.

Traefik and Acme.sh Instead of DNS-01
· ☕ 13 min read · ✍️ Mark A. McFate
This post is a follow-up to Dockerized Traefik Host Using ACME DNS-01 Challenge. It introduces an alternative to the failed process that was proposed in that earlier post. Note that the following config-specific elements have been replaced below: 6 occurances of ?

Simplified Testing of Traefik 2 with ACME DNS-01 Challenge
· ☕ 3 min read · ✍️ Mark A. McFate
This post is a simplified and focused follow-up to Dockerized Traefik Host Using ACME DNS-01 Challenge. Simplify Today, 19-May-2020, I’m going to take a shot at simplifying my testing on dgdocker3.grinnell.edu by removing unnecessary things and consolidating as much as possible to reduce clutter in the logs and get right to the point.

Dockerized Traefik Host Using ACME DNS-01 Challenge
· ☕ 11 min read · ✍️ Mark A. McFate
This post builds on My dockerized-server Config and attempts to change what was a problematic ACME HTTP-01 or httpChallenge in Traefik and Let’s Encrypt to an ACME DNS-01 or dnsChallenge. The problem with the old HTTP-01 or httpChallenge is that it requires the creation of a valid and widely accessible “A” record in our DNS before the creation of a cert; the record has to be in place so that the Let’s Encrypt CA-server can find it to confirm that the request is valid.