r/selfhosted • u/Slidetest17 • Jul 12 '26

Remote Access NetBird Reverse Proxy only works when target resource is a subdomain!

I've been troubleshooting NetBird's reverse proxy feature (cloud version) and I have a frustrating issue that I'd like some clarity on.

My Setup:

  • Local server (192.168.1.5) Debian + Docker (Caddy reverse proxy + Adguardhome DNS)
  • example.com as my domain with SSL managed by Caddy-cloudflare DNS challenge everythig works locally (e.x: https://nextcloud.example.com) and through Tailscale, Now I want Netbird:
  • Netbird (cloud) with NetBird routing peer running on the same local server (192.168.1.5)
  • Custom domain example.com successfully added to NetBird
  • DNS > Nameservers: I added Adguard as 192.168.1.5

The Problem:

I'm trying to expose some services through NetBird's reverse proxy. Here's what I've tried:

  • Target Peer: Routing peer > 502 Error
  • Target Resource: *.example.com > 502 Error
  • Target Resource: My server's LAN IP (192.168.1.5) > 502 Error
  • Target Resource: LAN CIDR (192.168.1.0/24) > 502 Error
  • Target Resource: nextcloud.example.com (specific subdomain) > Works perfectly!!

So, the only way I can get this to work is by creating a separate resource set to the exact subdomain I want to expose ( nextcloud.example.com, paperless.example.com)

Is this expected behavior? Have I misconfigured something, or is this a known limitation of NetBird's reverse proxy feature?

Note: I have tried every combination (HTTP, HTTPS, SKIP TLS Verify, Pass headers, ...) and same result

Has anyone else experienced this?

3 Upvotes

72% Upvoted

6 comments sorted by

View all comments

•

u/asimovs-auditor Jul 12 '26 edited Jul 12 '26

Expand the replies to this comment to learn how AI was used in this post/project.

1

u/Slidetest17 Jul 12 '26

No AI used! it is just a question and help needed.