[GH-ISSUE #5556] [Feature Request] Reverse Proxy: Allow Auth Bypass based on Source IP / CIDR #10770

Open
opened 2026-08-05 01:27:13 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @NoNaccc on GitHub (Mar 9, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5556

First of all, i love the new proxy feature!!

Is your feature request related to a problem? Please describe.
Yes. It's frustrating that the new built-in Reverse Proxy forces authentication for all requests, even if the device is already securely connected to the Netbird VPN network.

Describe the solution you'd like
I would like an option to bypass proxy authentication (SSO/Password) based on the Source IP or CIDR. For example, allowing the internal Netbird subnet (e.g., 100.64.0.0/10) to connect without facing an additional login screen.

Describe alternatives you've considered

  • Bypassing the proxy entirely via Split-DNS directly to the target server, but this breaks the SSL certificate on the endpoint.
  • Setting up a third-party proxy like Pangolin or a custom Traefik instance that supports IP whitelisting. However, I'd prefer to use Netbird's convenient all-in-one proxy solution.

Additional context
This is specifically needed for Split-DNS setups: Active VPN clients resolve the domain to the Netbird proxy's internal IP. This keeps the SSL certificate valid, but currently forces a redundant SSO login for users who are already authenticated via the VPN.

Originally created by @NoNaccc on GitHub (Mar 9, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5556 First of all, i love the new proxy feature!! **Is your feature request related to a problem? Please describe.** Yes. It's frustrating that the new built-in Reverse Proxy forces authentication for all requests, even if the device is already securely connected to the Netbird VPN network. **Describe the solution you'd like** I would like an option to bypass proxy authentication (SSO/Password) based on the Source IP or CIDR. For example, allowing the internal Netbird subnet (e.g., 100.64.0.0/10) to connect without facing an additional login screen. **Describe alternatives you've considered** - Bypassing the proxy entirely via Split-DNS directly to the target server, but this breaks the SSL certificate on the endpoint. - Setting up a third-party proxy like Pangolin or a custom Traefik instance that supports IP whitelisting. However, I'd prefer to use Netbird's convenient all-in-one proxy solution. **Additional context** This is specifically needed for Split-DNS setups: Active VPN clients resolve the domain to the Netbird proxy's internal IP. This keeps the SSL certificate valid, but currently forces a redundant SSO login for users who are already authenticated via the VPN.
saavagebueno added the feature-request label 2026-08-05 01:27:13 -04:00
Author
Owner

@sonalys commented on GitHub (Mar 21, 2026):

I'm also finding it hard to filter the reverse proxy based on an external ip.

I want to have a dns pointing to an internal service, which would provide both https and only being accessible through the intranet.

<!-- gh-comment-id:4103103177 --> @sonalys commented on GitHub (Mar 21, 2026): I'm also finding it hard to filter the reverse proxy based on an external ip. I want to have a dns pointing to an internal service, which would provide both https and only being accessible through the intranet.
Author
Owner

@NoNaccc commented on GitHub (Apr 18, 2026):

Update: since opening this issue, CIDR-based access restrictions have been added to the reverse proxy (allowed/blocked CIDRs per service). That's a step in the right direction, but it doesn't address the core ask here - those restrictions control who can connect, not who has to authenticate. There's still no way to say "if the source is in 100.64.0.0/16, skip SSO/password and let them through."

My use case remains the same: in a Split-DNS setup, VPN-connected clients hit the reverse proxy via its NetBird IP. The TLS cert is valid, the connection is already secured by WireGuard - but they still get an SSO login screen. That's the friction I want to eliminate.

Since I opened this, several related issues have come up that all circle the same broader gap:

  • #5413 - reverse proxy with custom DNS zones as domain source, no public ACME needed
  • #5400 - restrict reverse proxy access to specific NetBird groups/peers, disable public exposure
  • #5895 - internal reverse proxy without needing proxy clusters at all
  • #5862 - OR logic for access restrictions (e.g. allow if country=DE OR source in 100.64.0.0/16)

All of these point to a missing "private reverse proxy" mode - combining the proxy's convenience (DNS names, automatic TLS, port abstraction) with internal-only scope. The building blocks are largely there: custom DNS zones exist, CIDR restrictions exist, the proxy infrastructure exists. What's missing is tying them together so that a service can be internal-only with optional auth bypass for trusted sources.

<!-- gh-comment-id:4274560271 --> @NoNaccc commented on GitHub (Apr 18, 2026): Update: since opening this issue, CIDR-based access restrictions have been added to the reverse proxy (allowed/blocked CIDRs per service). That's a step in the right direction, but it doesn't address the core ask here - those restrictions control **who can connect**, not **who has to authenticate**. There's still no way to say "if the source is in 100.64.0.0/16, skip SSO/password and let them through." My use case remains the same: in a Split-DNS setup, VPN-connected clients hit the reverse proxy via its NetBird IP. The TLS cert is valid, the connection is already secured by WireGuard - but they still get an SSO login screen. That's the friction I want to eliminate. Since I opened this, several related issues have come up that all circle the same broader gap: - #5413 - reverse proxy with custom DNS zones as domain source, no public ACME needed - #5400 - restrict reverse proxy access to specific NetBird groups/peers, disable public exposure - #5895 - internal reverse proxy without needing proxy clusters at all - #5862 - OR logic for access restrictions (e.g. allow if country=DE OR source in 100.64.0.0/16) All of these point to a missing "private reverse proxy" mode - combining the proxy's convenience (DNS names, automatic TLS, port abstraction) with internal-only scope. The building blocks are largely there: custom DNS zones exist, CIDR restrictions exist, the proxy infrastructure exists. What's missing is tying them together so that a service can be internal-only with optional auth bypass for trusted sources.
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10770