mirror of
https://github.com/Dokploy/templates.git
synced 2026-07-10 00:15:28 +02:00
0ada7ae5f2
The Multica backend is an API-only chi server with no route registered at "/", so the generated backend domain (path "/") permanently answered HTTP 404 even though the container was healthy. The web frontend already proxies /api/*, /ws, /auth/* and /uploads/* to http://backend:8080 via Next.js rewrites, and when NEXT_PUBLIC_WS_URL is unset the browser derives the WebSocket URL from the page origin, so the backend never needs to be exposed publicly. - drop the backend [[config.domains]] entry and api_domain variable - drop NEXT_PUBLIC_WS_URL so the WS URL falls back to the page origin and goes through the frontend's /ws rewrite - remove ephemeral host port publications (ports: "8080"/"3000"); Traefik reaches the containers over the docker network Verified on a Dokploy instance: deploy done, frontend / -> 200 and backend reachable through the proxy (/api/config -> 200). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
