traefik-multi-network-container-backend-routing-failure
When a container is attached to multiple Docker networks and Traefik has no traefik.docker.network label, Traefik picks whichever network IP it resolves first — which may be an internal network Traefik cannot reach, causing backend timeouts. Fix: add traefik.docker.network=<network-traefik-is-on> label to the container’s compose service and recreate the container. Affected container: researchclaw on mcp-global-network + graphiti_oracle-internal.
Related
- traefik-multi-network-backend-picks-wrong-ip
- traefik-multi-network-container-backend-resolution
- traefik
- traefik-multi-network-label-missing-causes-504s
- graphiti
- 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
- traefik-multi-network-missing-label-routes-wrong-ip
- traefik-multi-network-missing-label-picks-wrong-backend-ip
- traefik-multi-network-container-missing-label-gotcha
- k8s-multi-doc-yaml-rejected-must-split-into-separate-files
- k8s-manifest-validator-rejects-multi-document-yaml