--- title: "Starting Internal Homeserver Services on Demand with Sablier on an Edge Server" date: 2026-11-16 tldr: "How I run Sablier on my public VPS edge server and point its DOCKER_HOST over WireGuard to my internal homeserver so Traefik can spin up containers on demand." tags: - Docker - Traefik - Self-Hosting - Homeserver - VPS layout: post.njk lang: en translationKey: sablier-edge-server-control --- I run a few services on my internal homeserver that I only need occasionally. Leaving them running 24/7 wastes RAM and power, but starting them manually via SSH every time I want to use them gets old fast. That's where **Sablier** comes in: it integrates with Traefik and automatically starts a Docker container when a request hits its URL, then stops it again after a period of inactivity. The catch? My Traefik reverse proxy runs on a public VPS **edge server**, while the actual containers live on my **internal homeserver** behind a WireGuard tunnel. ## The Setup Running Sablier on the edge server is surprisingly simple—you don't need Sablier on the internal server at all. You just point Sablier's `DOCKER_HOST` to the internal server's Docker socket (exposed over the private WireGuard network, e.g., via a Docker socket proxy): ```yaml services: sablier: image: sablierapp/sablier:latest container_name: sablier restart: unless-stopped command: - start - --provider.name=docker environment: - DOCKER_HOST=tcp://10.1.0.3:2375 - TZ=Europe/Berlin networks: - traefik networks: traefik: external: true ``` ## How It Works 1. **Traefik** on the edge server receives an incoming HTTPS request for a service. 2. The **Sablier middleware** intercepts the request and calls `sablier:10000` on the shared `traefik` Docker network. 3. **Sablier** connects to `tcp://10.1.0.3:2375` over WireGuard, checks if the target container on the internal homeserver is running, and starts it if needed. 4. Once the container is healthy, Traefik forwards the request to the internal server. After the configured `sessionDuration` of inactivity, Sablier stops the container again. ## Things to Keep in Mind - **Secure the Docker API**: Never expose port `2375` on a public interface. Keep it strictly bound to your private WireGuard IP (`10.1.0.3`) or behind a read/write-restricted Docker socket proxy. - **Startup time**: If a container takes a few seconds to boot, Sablier's built-in waiting screen (or blocking mode) handles the wait cleanly without Traefik returning a `502 Bad Gateway`. It's a tiny `docker-compose.yml`, and it lets me keep my homeserver lean while still having everything available on demand.