fix(frontend): bind Next to 0.0.0.0 so healthcheck passes (unhealthy fix) #1075

Merged

bot-backend merged 1 commit from fix/frontend-healthcheck-hostname into main

2026-06-06 15:07:10 +00:00

Author	SHA1	Message	Date
Light1YT	b77e856d89	fix(frontend): bind Next standalone to 0.0.0.0 so healthcheck passes All checks were successful CI / changes (push) Successful in 7s Details CI / changes (pull_request) Successful in 6s Details CI / backend-tests (push) Has been skipped Details CI / backend-tests (pull_request) Has been skipped Details Deploy / changes (push) Successful in 5s Details Deploy / build-backend (push) Has been skipped Details Deploy / build-worker (push) Has been skipped Details Deploy / build-frontend (push) Successful in 2m46s Details Deploy / deploy (push) Successful in 50s Details Docker auto-sets HOSTNAME to the container id; Next standalone's server.js binds process.env.HOSTNAME, so it listened on the container hostname and the compose healthcheck (TCP 127.0.0.1:3000) was refused → frontend container chronically "(unhealthy)" (cosmetic: Caddy reaches it by service name and the site serves 200). Pin HOSTNAME=0.0.0.0 — the canonical Next.js Docker fix. Diagnosed on prod 2026-06-05.	2026-06-06 20:06:52 +05:00