haproxy-letsencrypt-docker.md
... ...
@@ -14,6 +14,6 @@ Docker and HAProxy and Let's Encrypt: minor pain in the arse.
14 14
15 15
There's a few things that make this a bit of a hassle:
16 16
1. We want haproxy to be running on port 80/443, but those are the ports certbot needs to do validation<br/>We'll have to do this in two stages.
17
-2. haproxy with the default config won't start up if it can't resolve the container IPs for the backends.<rb/>Since certbot is just a command to be run in a container, it probably won't be running when haproxy starts up.
17
+2. haproxy with the default config won't start up if it can't resolve the container IPs for the backends.<br/>Since certbot is just a command to be run in a container, it probably won't be running when haproxy starts up.
18 18
3. certbot needs to be run once in one way to request the certs, and then every couple of days/weeks in another way to check and renew certs.<br/>We'll need to different incantations for certbot.
19 19
4. When the certs are renewed, we'll need to tell haproxy to pick them up<br/>Some docker-in-dockr magic is required.