Part 3 — Traefik and SSL

Part 3 of 7 — Self-hosting Supabase: a learning journey We need a reverse proxy. It sits in front of all our containers, terminates TLS, and routes incoming requests to the right service based on the hostname. Traefik is the standard choice for Docker-based setups because it can read container labels and configure itself automatically. Add a label to a container saying "I want a route at this domain" and Traefik creates it. This is elegant. It also has a compatibility problem I ran into immediately, and that costed me quite some time. The version problem Recent versions of Docker Engine changed the way the API negotiates versions with clients. Traefik v2, the version you will find in most tutorials, does not handle this correctly. It connects to the Docker daemon, appears to start fine, but silently fails to pick up any services. Your containers are running. Traefik is running. Nothing gets routed. There is no error message that points clearly at the cause. The fix is Traefik v3, the c