Issue routing to backends via multiple network interfaces on macOS

Traefik Traefik v3 (latest)
,
1

I've got Traefik 3.3 set up via home-brew on my Mac (macOS Seqoia on Apple Silicon) and trying to proxy pass to a service running on a virtual machine on my Mac. I've configured the entry points on Traefik and also the services and routers to reach a web server inside a virtual machine. The only provider I've configured is "file" as Traefik is not running in containers or anything else.

When I try to get to the URL on Traefik on my Mac, I'm getting a "bad gateway" error.

The virtual machine is on the network 192.168.77.0/24 and the Mac obviously has an interface on that network (bridge100 in my case). When I call the service from the Mac Termin via Curl or from the browser directly on its Address http://192.168.77.2:3000 it's working just fine. But Traefik is complaining that it can't reach the backend:

2025-02-24T13:07:01+01:00 DBG github.com/traefik/traefik/v3/pkg/proxy/httputil/proxy.go:117 > 502 Bad Gateway error="dial tcp 192.168.77.2:3000: connect: no route to host"

::1 - - [24/Feb/2025:12:07:01 +0000] "GET /openwebui/ HTTP/1.1" 502 11 "-" "-" 266 "openwebui@file" "http://192.168.77.2:3000/" 9ms

Any idea why Traefik can't reach the backend? It should just route via the bridge100 interface, right?

2

You are running Traefik as binary directly on Mac without container? Then it should use the same networking as curl on CLI.

3

yes, running Traefik as macOS binary. That's why I'm expecting it should be able to reach the backend as every other binary seems to be able too.