diff --git a/Run-Blob-Storage-on-Public-Internet.md b/Run-Blob-Storage-on-Public-Internet.md
index f9f3174..6b86c92 100644
--- a/Run-Blob-Storage-on-Public-Internet.md
+++ b/Run-Blob-Storage-on-Public-Internet.md
@@ -144,7 +144,7 @@ services:
 I haven't tested this, but this is how I would go about making it HA:
 - Run master server on 3 or 5 physical servers
 - Run caddy as a sidecar on every server that runs a master
-- Install caddy from own Dockerfile, adding [redis plugin](github.com/gamalan/caddy-tlsredis) for distributed SSL cert storage and distributed locks for SSL cert issuing.
+- Install caddy from own Dockerfile, adding [redis plugin](https://github.com/gamalan/caddy-tlsredis) for distributed SSL cert storage and distributed locks for SSL cert issuing.
 - Run redis in high-availability mode, for example by [following this docker swarm guide](https://medium.com/@emmano3h/redis-high-availability-with-docker-swarm-2142a4d80b49). Caddy redis plugin probably doesn't allow multiple IP addresses, so might have to add `haproxy` sidecar to every caddy sidecar as well to load balance to redis cluster.
 - Update `command` of volume servers docker-compose file to add all master server IPs