{
  "id": 10718021,
  "title": "My Traefik Set Up on Docker",
  "url": "https://urgent.news/2026/09/29/my-traefik-set-up-on-docker",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-29T15:22:53.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/leomalavera/my-traefik-set-up-on-docker-1ki7"
  },
  "original_language": "en",
  "account": "A Simple Reverse Proxy for My Homelab\n\nRunning several services on Docker led to managing ports, domains, HTTPS certificates, and reverse-proxy configuration manually, which became tedious. Using Traefik addressed this issue by allowing Traefik to discover Docker containers and route traffic based on labels.\n\nThe Setup\nSeveral services, such as Pi-hole, Vaultwarden, applications, and monitoring tools, were running on the same server. A reverse proxy was needed to simplify the URLs, enable HTTPS, and reduce manual configurations.\n\nArchitecture\nTraefik acted as the reverse proxy, with Docker containers running inside a dedicated Docker network. Docker Compose was used to create the network and define the Traefik container. Traefik inspected Docker containers using the Docker socket mounted as read-only.\n\nTraefik Configuration\nTraefik required minimal static configuration. It had an API dashboard enabled, consumed Docker events via the Docker socket, and configured entry points for HTTP and HTTPS. The ACME integration for Let's Encrypt was also set up for automated certificate management.\n\nRouting with Docker Labels\nTraefik's power lay in its ability to automatically route traffic based on Docker labels. By adding specific labels to their services, users could define the routing rules, HTTP/HTTPS protocols, and certificate resolution.\n\nHTTPS\nLet's Encrypt was integrated with Traefik's ACME functionality, allowing for automatic certificate issuance and renewal. Services could easily reference the Let's Encrypt certificate resolver in their Traefik configuration.\n\nHTTP → HTTPS Redirection\nHTTP traffic could be redirected to HTTPS for enhanced security. This redirection was configured within Traefik's entry points, ensuring a smooth transition from HTTP to HTTPS.",
  "summary": "My Traefik Setup with Docker: A Simple Reverse Proxy for My Homelab I've been running several services on Docker, and at some point managing ports, domains, HTTPS certificates, and reverse-proxy configuration manually became annoying. That's where Traefik became useful. Instead of configuring Nginx every time I deploy a new service, I can let Traefik discover my Docker containers and route…",
  "key_points": [
    "Traefik simplifies reverse proxy configuration for Docker containers",
    "Docker Compose creates dedicated network for Traefik and services",
    "Traefik routes traffic based on Docker labels and HTTPS certificates"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}