[GH-ISSUE #5400] Access to reverse proxy only for certain groups #11367

Open
opened 2026-08-05 01:29:28 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @JeWe37 on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5400

Is your feature request related to a problem? Please describe.
Netbirds new reverse proxy makes otherwise rather complex SSO authentication for proxies services, as well as TLS certificates simple. However one might prefer some services to only be accessible within the Netbird network rather than be publicly exposed.

Describe the solution you'd like
Allow selecting netbird groups/peers which are allowed to access a reverse proxy service, disable the publicly exposed reverse proxy if this is enabled.

Describe alternatives you've considered
Just using Netbirds normal DNS hosts does not allow for HTTPS access(which is necessary for e2ee if accessing from a (properly routed) Netbird subnet and assuming the hosts themselves don't handle that) and does not work for having multiple services on one host, unless one wants to use non standard ports.

Authentication via SSO, password or similar alone is a given, but not all services should be accessible from the outside. You may not trust exposing them directly, especially when they bring their own potentially less trustworthy authentication that you don't want to duplicate.

Additional context
For me this would be the one feature missing for Netbird to essentially be a completely integrated zero trust networking solution for my homelab. Doing the same thing is entirely possible for example with traefik/envoy and mTLS, as well as oauth2-proxy and Keycloak, but would involve substantial added complexity.

Originally created by @JeWe37 on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5400 **Is your feature request related to a problem? Please describe.** Netbirds new reverse proxy makes otherwise rather complex SSO authentication for proxies services, as well as TLS certificates simple. However one might prefer some services to only be accessible within the Netbird network rather than be publicly exposed. **Describe the solution you'd like** Allow selecting netbird groups/peers which are allowed to access a reverse proxy service, disable the publicly exposed reverse proxy if this is enabled. **Describe alternatives you've considered** Just using Netbirds normal DNS hosts does not allow for HTTPS access(which is necessary for e2ee if accessing from a (properly routed) Netbird subnet and assuming the hosts themselves don't handle that) and does not work for having multiple services on one host, unless one wants to use non standard ports. Authentication via SSO, password or similar alone is a given, but not all services should be accessible from the outside. You may not trust exposing them directly, especially when they bring their own potentially less trustworthy authentication that you don't want to duplicate. **Additional context** For me this would be the one feature missing for Netbird to essentially be a completely integrated zero trust networking solution for my homelab. Doing the same thing is entirely possible for example with traefik/envoy and mTLS, as well as oauth2-proxy and Keycloak, but would involve substantial added complexity.
saavagebueno added the feature-request label 2026-08-05 01:29:28 -04:00
Author
Owner

@polaroidkidd commented on GitHub (Feb 22, 2026):

I'd be very interested in this aswell. It would essentially eliminate the need for a split-horizon DNS, which in itself is a pain to setup and maintain in addition to which a separate service needs to handle SSL certificates.

This would allow you to define a sidecar container for a proxy which exposes a containerized application exclusively via netbird vpn while still allowing for SSL certificates and port mapping.

<!-- gh-comment-id:3941866309 --> @polaroidkidd commented on GitHub (Feb 22, 2026): I'd be very interested in this aswell. It would essentially eliminate the need for a split-horizon DNS, which in itself is a pain to setup and maintain in addition to which a separate service needs to handle SSL certificates. This would allow you to define a sidecar container for a proxy which exposes a containerized application exclusively via netbird vpn while still allowing for SSL certificates and port mapping.
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#11367