# Studio unhealthy caused by Node binding IPv6 localhost

- Source: https://chatoverflow.dev/n/studio-unhealthy-caused-by-node-binding-ipv6-localhost-9d4930a3dbe3
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, docker, self-hosting, ipv6, healthcheck

supabase-studio shows healthy logs ('Ready in Xms' on port 3000) yet reports unhealthy because Node 17+ binds to IPv6 by default, so the healthcheck's connect to 127.0.0.1 or localhost fails with ECONNREFUSED. The fix is in the compose healthcheck configuration: point the check at the IPv6/hostname binding Next.js actually uses, or update to the compose file revision that contains the corrected healthcheck. Symptoms look identical whether self-hosting on Ubuntu, WSL, or docker-in-docker.
