SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-18 22:22:14 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

TLS/SSL Handling for Netbird Domain #944

New Issue
Open
opened 2025-11-20 05:20:21 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 05:20:21 -05:00
Owner
Copy Link

Originally created by @Thunderbottom on GitHub (May 30, 2024).

Is your feature request related to a problem? Please describe.
Currently the only TLS/SSL being used is the one that wireguard brings. We would like to have SSL connection to endpoints running over netbird for services that can be accessed through the configured netbird domain (eg. peer.netbird.domain).

Describe the solution you'd like

  1. A way for netbird to handle TLS/SSL termination for the netbird domain.
  2. A way to configure TLS/SSL for such endpoints.

Maybe a wildcard certificate can be generated, and trusted in the root CA for all the netbird registered peers, so service-level SSL can be made possible. If netbird is to not handle the termination, the certificates can be placed in some directory on the peer, and can be utilised within the reverse proxy or application configuration.

Describe alternatives you've considered
Currently none, but can use self-signed certificates and install on each node manually. This process can be automated through netbird since it already allows access through the configured domain.

Additional context
N/A

Originally created by @Thunderbottom on GitHub (May 30, 2024). **Is your feature request related to a problem? Please describe.** Currently the only TLS/SSL being used is the one that wireguard brings. We would like to have SSL connection to endpoints running over netbird for services that can be accessed through the configured netbird domain (eg. `peer.netbird.domain`). **Describe the solution you'd like** 1. A way for netbird to handle TLS/SSL termination for the netbird domain. 2. A way to configure TLS/SSL for such endpoints. Maybe a wildcard certificate can be generated, and trusted in the root CA for all the netbird registered peers, so service-level SSL can be made possible. If netbird is to not handle the termination, the certificates can be placed in some directory on the peer, and can be utilised within the reverse proxy or application configuration. **Describe alternatives you've considered** Currently none, but can use self-signed certificates and install on each node manually. This process can be automated through netbird since it already allows access through the configured domain. **Additional context** N/A
saavagebueno added the feature-request label 2025-11-20 05:20:21 -05:00
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

Sounds more like a feature request for NetBird client to have a reverse proxy built-in?

@nazarewk commented on GitHub (Apr 23, 2025): Sounds more like a feature request for NetBird client to have a reverse proxy built-in?
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

@Thunderbottom commented on GitHub (Apr 23, 2025):

Ideally, yes, more like a forward-proxy rather than a reverse-proxy. This would allow us to apply ACLs to Netbird peers and only allow those with access to connect to these websites internally.

@Thunderbottom commented on GitHub (Apr 23, 2025): Ideally, yes, more like a forward-proxy rather than a reverse-proxy. This would allow us to apply ACLs to Netbird peers and only allow those with access to connect to these websites internally.
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

@Thunderbottom commented on GitHub (Apr 23, 2025):

Right now NetBird sort of does the same thing, the only piece missing is the SSL management part which is left to the peer to handle. We'd like NetBird to manage TLS/SSL so there's no requirement for a setup on the peer's end.

@Thunderbottom commented on GitHub (Apr 23, 2025): Right now NetBird sort of does the same thing, the only piece missing is the SSL management part which is left to the peer to handle. We'd like NetBird to manage TLS/SSL so there's no requirement for a setup on the peer's end.
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

@BillyatGithub commented on GitHub (Jul 25, 2025):

TLS certificate management built into the NetBird clients would make the onboarding process for friends and family a lot easier. Instead of installing the certs on every endpoint manually, which already looks very sketchy from the viewpoint of the uninformed end user, the whole device enrollment into NetBird would become completely transparent.

@BillyatGithub commented on GitHub (Jul 25, 2025): TLS certificate management built into the NetBird clients would make the onboarding process for friends and family a lot easier. Instead of installing the certs on every endpoint manually, which already looks very sketchy from the viewpoint of the uninformed end user, the whole device enrollment into NetBird would become completely transparent.
saavagebueno commented 2025-11-20 05:20:23 -05:00
Author
Owner
Copy Link

@nhanpc commented on GitHub (Nov 6, 2025):

+1

@nhanpc commented on GitHub (Nov 6, 2025): +1
saavagebueno commented 2025-11-20 05:20:23 -05:00
Author
Owner
Copy Link

@sundbp commented on GitHub (Nov 10, 2025):

+1 (something like the tailscale TLS feature would be great: https://tailscale.com/kb/1153/enabling-https)

@sundbp commented on GitHub (Nov 10, 2025): +1 (something like the tailscale TLS feature would be great: https://tailscale.com/kb/1153/enabling-https)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#944
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?