traefik-multi-network-backend-resolution-failure

When a container belongs to multiple Docker networks and lacks a traefik.docker.network label, Traefik picks an arbitrary network IP that may be unreachable. Fix: add traefik.docker.network=<correct-network> label to the container and recreate it. researchclaw was on mcp-global-network + graphiti_oracle-internal; Traefik chose the internal IP (172.19.0.6) which it couldn’t route to.

Related

• traefik-multi-network-backend-picks-wrong-ip
• traefik-multi-network-container-backend-resolution
• traefik-multi-network-container-backend-routing-failure
• traefik
• traefik-multi-network-container-requires-explicit-network-la