fix blocked connection

Inside a Docker container, 127.0.0.1 refuses connections coming from Dokploy's internal proxy. We can bypass this easily by installing socat—a lightweight network relay—inside the container. It acts as a safe bridge: Dokploy talks to socat on 0.0.0.0:3080, and socat passes the traffic internally to the app on 127.0.0.1:3081.
2026-09-03 15:17:10 +00:00 · 2026-09-03 15:17:10 +00:00 · 333af4c0ea
commit 333af4c0ea
parent adf5259868
1 changed files with 8 additions and 6 deletions
--- a/14
+++ b/14
@ -1,18 +1,20 @@
 FROM node:22-bookworm

+# Install socat to forward traffic safely inside the container
+RUN apt-get update && apt-get install -y socat && rm -rf /var/lib/apt/lists/*
+
 WORKDIR /app

-# Enable pnpm automatically
+# Enable pnpm
 RUN corepack enable && corepack prepare pnpm@latest --activate

-# Copy repository source code
+# Copy code and build
 COPY . .
-
-# Install dependencies and build
 RUN pnpm install
 RUN pnpm run build

 EXPOSE 3080

-# Force 0.0.0.0 host binding and disable browser popups
-CMD ["node", "--import", "tsx/esm", "apps/cli/src/bin.ts", "web", "--host", "0.0.0.0", "--no-open"]
+# Forward Dokploy traffic (3080) to app loopback (3081)
+CMD socat TCP-LISTEN:3080,fork,reuseaddr TCP:127.0.0.1:3081 & \
+    node --import tsx/esm apps/cli/src/bin.ts web --port 3081 --no-open