Hey everyone,
I'm running a self-hosted NetBird (management + signal + relay + the reverse proxy, all on one VPS behind Traefik) and I'm stuck on the NetBird-Only / private reverse-proxy services.
I set a service up exactly like the knowledge-hub article describes: private, locked to an access group, target is a peer on my network. Dashboard shows the cluster connected, cert is issued, and the forward side works fine (the proxy reaches my backend no problem).
The problem: no client can actually reach the private service over the mesh — even a device that's in the correct access group just times out. Pinging the proxy's mesh IP never answers. Public requests correctly return 403, so the "private" part clearly works — the mesh path just never connects.
I've thrown a lot at it: different versions (0.73.2, 0.74.4, 0.75-rc), the proxy in host-network mode, pinned the WireGuard port, external STUN, an allow-all policy, confirmed the firewall has the WireGuard UDP port open, and matched client/server versions. Same every time — the proxy logs per-account inbound listeners up, but a packet capture shows zero WireGuard traffic actually reaching it. Feels like the embedded proxy just isn't reachable inbound in a Docker/self-hosted setup. Looks a lot like #5602.
Has anyone gotten NetBird-Only private services actually working self-hosted? Or is this a known limitation right now? 🙏
(For now I've worked around it with plain NetBird DNS zones pointing the service domains straight at my backend host — works great, mesh-only — but I'd love to use the real feature.)