From 68549637d7ffc8c241d45c475c396e1f25c10aa7 Mon Sep 17 00:00:00 2001 From: Ihor_Zhekov Date: Fri, 12 Jun 2026 11:31:25 +0200 Subject: [PATCH] Attach frontend to external coolify network so Traefik can route Coolify's Traefik defaults to the 'coolify' network, but the frontend was only on the per-resource network -> Traefik couldn't reach it (000/empty reply). Join the external coolify network + set traefik.docker.network=coolify. Co-Authored-By: Claude Opus 4.8 --- docker-compose.yml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index 1babec2..8c0916c 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -29,6 +29,8 @@ services: # Persist the SQLite file across container rebuilds. - visigine_data:/data restart: unless-stopped + networks: + - default frontend: build: @@ -41,6 +43,18 @@ services: backend: condition: service_healthy restart: unless-stopped + # Join Coolify's proxy network so Traefik (which defaults to the `coolify` + # network) can reach this container, and point Traefik at that network + # explicitly since the container is attached to several. + networks: + - default + - coolify + labels: + - "traefik.docker.network=coolify" + +networks: + coolify: + external: true volumes: visigine_data: