From 6d025dfafc0d41dcbbd3a73277807cb84a573de0 Mon Sep 17 00:00:00 2001 From: Pankaj Kumar Bind Date: Fri, 24 Apr 2026 00:51:09 +0530 Subject: [PATCH] fix(network): give backend outbound internet access The backend was attached only to the 'internal' network, which is marked 'internal: true' -- Docker disallows any outbound traffic from that network, so the container couldn't resolve challenges.cloudflare.com (Turnstile), smtp.gmail.com (email), Sentry, HaveIBeenPwned, etc. Fix: attach backend to 'external' as well. Still no inbound exposure (no ports published on backend), only outbound becomes possible. DB remains on 'internal' only. --- docker-compose.oracle.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docker-compose.oracle.yml b/docker-compose.oracle.yml index 69868c3..5dd8d6f 100644 --- a/docker-compose.oracle.yml +++ b/docker-compose.oracle.yml @@ -90,7 +90,13 @@ services: - static_files:/app/staticfiles - media_files:/app/media networks: + # `internal` for DB access (DB stays unreachable from the internet). + # `external` so the backend itself can make OUTBOUND calls to + # Cloudflare Turnstile, Gmail SMTP, Sentry, HaveIBeenPwned, etc. + # (The backend never publishes its port, so outbound access here + # does not expose it to inbound internet traffic.) - internal + - external deploy: resources: limits: