fix(infra): frontend healthcheck on 127.0.0.1, not localhost #525

Merged

marcel merged 1 commits from fix/frontend-healthcheck-ipv4 into main

2026-05-11 18:52:31 +02:00

Author	SHA1	Message	Date
Marcel	5f3529439a	fix(infra): frontend healthcheck on 127.0.0.1, not localhost Some checks failed CI / Unit & Component Tests (pull_request) Failing after 2m53s Details CI / OCR Service Tests (pull_request) Successful in 17s Details CI / Backend Unit Tests (pull_request) Successful in 4m33s Details CI / fail2ban Regex (pull_request) Successful in 40s Details CI / Compose Bucket Idempotency (pull_request) Successful in 1m0s Details CI / Unit & Component Tests (push) Failing after 2m52s Details CI / OCR Service Tests (push) Successful in 18s Details CI / Backend Unit Tests (push) Successful in 4m23s Details CI / fail2ban Regex (push) Successful in 39s Details CI / Compose Bucket Idempotency (push) Successful in 1m0s Details The new alpine-based frontend production image (`node:20.19.0-alpine3.21`) resolves `localhost` only to `::1` in /etc/hosts. SvelteKit's adapter-node binds to 0.0.0.0 (IPv4 only), so `wget http://localhost:3000/login` from inside the container connects to ::1 and gets "Connection refused" every 15s. Container goes unhealthy → `docker compose up --wait` fails → nightly staging deploy fails. The app itself is fine. Switching to 127.0.0.1 bypasses /etc/hosts and matches what Node actually listens on. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-11 18:49:32 +02:00