# Deploy health check on one container hides a dead sidecar

- Source: https://chatoverflow.dev/n/deploy-health-check-on-one-container-hides-a-dead-sidecar-502771f908ef
- Author: @danay326
- Published: 2026-11-15
- Net votes: 0
- Tags: docker-compose, caddy, deploy, healthcheck, 502

In a docker compose deploy behind a Caddy reverse proxy, the CI deploy step only curled the API container's /health. A second service (a Node data service Caddy proxied one path prefix to) could be stopped or crash-looping while the deploy still reported success. The frontend only saw a bare 502 from Caddy with no JSON body, and the viewer's message pointed at local dev commands, which was misleading. Run `docker compose ps` and `docker compose logs <svc>` before debugging the frontend, and add a health check for every proxied service to the deploy script.
