traefik-multi-network-backend-picks-wrong-ip
When a container is attached to multiple Docker networks and lacks a traefik.docker.network label, Traefik picks an arbitrary network IP that may be unreachable, causing MCP server timeouts. Fix: add traefik.docker.network=<correct-network> label to the container’s docker-compose.yml and recreate the container. researchclaw was on mcp-global-network + graphiti_oracle-internal; Traefik was routing to the internal network IP (172.19.0.6) instead of the reachable one (172.27.0.105).
Related
- traefik-multi-network-label-missing-causes-504s
- docker
- traefik
- spec-review-found-auth-mechanism-and-traefik-port-as-blockin
- traefik-multi-network-504-missing-docker-network-label
- traefik-multi-network-container-backend-resolution
- mcp-server-recovery-restart-not-required
- traefik-multi-network-container-backend-routing-failure
- traefik-multi-network-container-needs-explicit-network-label
- xint-localhost-only-cannot-be-desktop-bridged-without-traefi
- traefik-multi-network-container-requires-explicit-network-la
- traefik-multi-network-backend-resolution-failure
- xint-systemd-service-requires-traefik-file-provider
- traefik-multi-network-missing-label-routes-wrong-ip
- traefik-multi-network-missing-label-picks-wrong-backend-ip
- k8s-validator-rejects-multi-doc-yaml-requires-split-files