From f47d3dc118c9b90250437674aa55d4b36934e3a2 Mon Sep 17 00:00:00 2001
From: kianiadee <kianiadee@gmail.com>
Date: Wed, 27 May 2026 22:56:31 +0300
Subject: [PATCH] Coolify compose: attach gateway to `coolify` external network
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Traefik runs on the `coolify` shared network. Without the gateway also
being on it, Traefik logs "Could not find network 'coolify' for
container, defaulting to first available" and picks an IP on the
project-local network it can't reach → intermittent 504 Gateway Timeout
(30s) in the browser.

Hot-patched the running container via `docker network connect coolify`;
this commit makes the fix permanent so the next Coolify redeploy doesn't
reintroduce the regression.

Worker and cron don't need it — they don't serve external HTTP.
---
 docker-compose.coolify.yml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docker-compose.coolify.yml b/docker-compose.coolify.yml
index 3ab3d7a..99e9fd0 100644
--- a/docker-compose.coolify.yml
+++ b/docker-compose.coolify.yml
@@ -28,6 +28,12 @@ networks:
   db_project:
     name: bo3nov2ija7g8wn9b1g2paxs
     external: true
+  # Traefik runs on `coolify`. The gateway must join it so Host(`api.rahamafresh.com`)
+  # actually resolves to a reachable IP; without it Traefik picks the wrong
+  # interface and times out at 30s → intermittent 504s in the browser.
+  coolify_shared:
+    name: coolify
+    external: true
 
 services:
   gateway:
@@ -37,6 +43,7 @@ services:
     networks:
       - default
       - db_project
+      - coolify_shared
     environment:
       APP_ROLE: gateway
       APP_MODE: prod