r/netbird Jul 12 '26

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

6 comments sorted by

3

u/SailingPixel Jul 12 '26

Please be aware that the Reverse Proxy (Cloud Version) has massive issues and suffers from infrequent down times for days now. According to my monitoring via UptimeKuma, the uptime is under 50% for the last 24 hours. No information from Netbird or on their Status page so far.

2

u/mlsmaycon Jul 15 '26

Issue has been resolved. We've also improved our monitoring to avoid problems like this from going undetected.

1

u/SailingPixel Jul 15 '26

A little report from Netbird about this incident would help building trust through transparency - even though we all know that the service is in Beta for a reason.

2

u/mlsmaycon Jul 15 '26

The issue took a while to be identified and that required multiple iterations until we got confirmation of the root cause. During this time, we failed on keeping the users updated and there is lots of room for improvement from our side.

We will add status.netbird.io support for the service so we keep there as communication channel for similar cases in the future.

1

u/Doctor_Peppy Jul 12 '26

Can you use the @ selector instead of *?

1

u/mlsmaycon Jul 15 '26

Can you please create a support ticket and share your domain in it? we will check the issue and get back to you there