From 0638d9c14331625b66e3420e90f9565712738f02 Mon Sep 17 00:00:00 2001
From: Tim Stollberg <tim.stollberg@mpm-it.com>
Date: Sat, 18 Jul 2026 15:58:40 +0700
Subject: [PATCH] fix(docker): remove redundant custom network from prod
 compose
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

nginx sat on two Docker networks (Coolify's shared per-app network,
where coolify-proxy lives, plus our custom "mandant" bridge). With
no explicit traefik.docker.network label, Traefik's Docker provider
picked one non-deterministically across deploys — when it picked
"mandant", its backend connection went to an unreachable network and
silently hung after completing the TLS/HTTP handshake with clients.

All services already share Coolify's injected network, so the custom
network was redundant. Removing it leaves each container on exactly
one network, eliminating the ambiguity.
---
 docker/docker-compose.prod.yml | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/docker/docker-compose.prod.yml b/docker/docker-compose.prod.yml
index 781a17f..b394c25 100644
--- a/docker/docker-compose.prod.yml
+++ b/docker/docker-compose.prod.yml
@@ -16,8 +16,6 @@ services:
     depends_on:
       mysql:
         condition: service_healthy
-    networks:
-      - mandant
 
   nginx:
     build:
@@ -27,8 +25,6 @@ services:
       - "8899:80"
     depends_on:
       - backend
-    networks:
-      - mandant
 
   mysql:
     image: mysql:8.0
@@ -44,12 +40,6 @@ services:
       interval: 5s
       timeout: 5s
       retries: 10
-    networks:
-      - mandant
 
 volumes:
   mysql_data:
-
-networks:
-  mandant:
-    driver: bridge