---
title: "Comment by Edge Ops on \"Securing Your Web App with Traefik: SSL Certificate & Reverse Proxy Setup Using Docker Compose\" | Hashnode"
description: "Traefik as the Compose front door with ACME on the HTTPS entrypoint is a clean pattern: one public listener, Host-based routers, and backends that never bind th"
url: "https://hashnode.com/posts/securing-your-web-app-with-traefik-ssl-certificate-and-reverse-proxy-setup-using-docker-compose/686c80524cea545770a696a5/comment/6aebbd2895bbdafcf619f041"
---

[Discussion](https://hashnode.com/posts/securing-your-web-app-with-traefik-ssl-certificate-and-reverse-proxy-setup-using-docker-compose/686c80524cea545770a696a5)

Comment [Securing Your Web App with Traefik: SSL Certificate & Reverse Proxy Setup Using Docker Compose](https://hashnode.com/posts/securing-your-web-app-with-traefik-ssl-certificate-and-reverse-proxy-setup-using-docker-compose/686c80524cea545770a696a5)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 4](https://hashnode.com/posts/securing-your-web-app-with-traefik-ssl-certificate-and-reverse-proxy-setup-using-docker-compose/686c80524cea545770a696a5/comment/6aebbd2895bbdafcf619f041)

Traefik as the Compose front door with ACME on the HTTPS entrypoint is a clean pattern: one public listener, Host-based routers, and backends that never bind the WAN. I keep the ACME storage volume durable across stack recreates, pin entrypoint names in every router rule, and separate the dashboard behind an allowlist or basic auth so it is not reachable from the same public routers that serve apps.

After a cert or label change I hit each hostname once and confirm the chain, the matched router, and that WebSocket or long-poll paths keep longer read timeouts than static routes. Also verify X-Forwarded-Proto and the real client address still arrive after Traefik terminates TLS — losing those headers after a compose bump looks like an app redirect bug when it is still the proxy hop.
