From 9d1a61885c8c1c6c27ab16fefa8812a1dbc6ea58 Mon Sep 17 00:00:00 2001 From: "Max R. Carrara" Date: Sat, 16 Aug 2025 22:52:06 +0200 Subject: [PATCH] server: docker: fix traefik not being able to discover server tl;dr: Since the server is in both the postgres instance's isolated "backend" network and the public-facing "docker-net", traefik unfortunately happened to decide to use the "backend" network for its proxying purposes. This led to the server not being reachable at all. This commit fixes that by explicitly telling traefik which network to use. Signed-off-by: Max R. Carrara --- wien_talks/wien_talks_server/docker-compose.deploy.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/wien_talks/wien_talks_server/docker-compose.deploy.yaml b/wien_talks/wien_talks_server/docker-compose.deploy.yaml index 1028fcd..9847ee1 100644 --- a/wien_talks/wien_talks_server/docker-compose.deploy.yaml +++ b/wien_talks/wien_talks_server/docker-compose.deploy.yaml @@ -62,6 +62,7 @@ services: - "traefik.http.routers.wien-talks-web.entrypoints=secure" - "traefik.http.routers.wien-talks-web.service=wien-talks-web-service" - "traefik.http.services.wien-talks-web-service.loadbalancer.server.port=${SERVERPOD_WEB_SERVER_PORT}" + - "traefik.docker.network=docker-net" volumes: db: