[GH-ISSUE #5479] [Feature Proposal] Internal HTTPS Certificates for Peer Resources #11544

New Issue

saavagebueno · 2026-08-05T01:29:59-04:00

saavagebueno commented

2026-08-05 01:29:59 -04:00

Originally created by @zgv163 on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5479

TL;DR: There's no way to get valid TLS certificates for NetBird peer hostnames (e.g., crm.netbird.cloud). Tailscale solved this years ago with tailscale cert. Two viable paths exist: an internal CA (potentially via Smallstep), or the brand-new Let's Encrypt DNS-PERSIST-01 challenge type arriving Q2 2026. Is this on the roadmap? Would a community PR be welcome?

The Gap

When you access services over NetBird peer domains, browsers throw security warnings because there's no valid TLS cert for the hostname. WireGuard encrypts the tunnel, but browsers don't know that.

The workarounds today aren't great:

Ignore the warnings (not acceptable when working in teams or production)
Set up a self-signed CA manually and install it on every device
Use the new Reverse Proxy, which is cool but always exposes things publicly, often the opposite of what you want

This keeps coming up and there hasn't been an official response yet:

[#2080](https://github.com/netbirdio/netbird/issues/2080) - 22+ 👍, open since May 2024
[#4903](https://github.com/netbirdio/netbird/issues/4903) - Dec 2025
[#5029](https://github.com/netbirdio/netbird/issues/5029) - Jan 2026, directly references Tailscale

Two Possible Approaches

Approach 1: Internal CA

The management server generates a root CA and signs certificates for peers on request. A netbird cert CLI command handles the flow. The peer's private key never leaves the device, only a CSR is sent.

This could be built from scratch using Go's crypto/x509 stdlib, or by integrating [Smallstep's step-ca](https://github.com/smallstep/certificates) which brings ACME support, auto-renewal, and certificate policies out of the box.

Pro: Works today, works for any domain including .selfhosted, .local, custom ones.
Con: Users need to trust the CA on their devices.

Approach 2: Let's Encrypt via DNS-PERSIST-01

Let's Encrypt announced DNS-PERSIST-01 in February 2026. It's a new ACME challenge where a single persistent DNS record authorizes an ACME account to issue certs for a domain and all its subdomains. No per-peer DNS updates needed, ever.

_validation-persist.netbird.cloud. IN TXT (
  "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/XXX; policy=wildcard"
)

Set it once, issue certs for any *.netbird.cloud subdomain indefinitely. Production rollout is expected Q2 2026.

Pro: Real publicly-trusted certs, zero trust store setup on client devices.
Con: Only works for NetBird-controlled domains (cloud users) or self-hosters with a public domain. Depends on LE timeline.

Where Should This Live?

Should this be part of the management server (which already knows all peer identities and has gRPC channels to every peer), or within the reverse proxy service as an extension? Management feels like the natural home since this is about internal resources, but curious what the team thinks.

The Ask

Is this planned? Even a rough timeframe helps the community plan around it.
Would a community PR for Approach 1 (internal CA) be welcome as a starting point?
For cloud users: could DNS-PERSIST-01 work with netbird.cloud once LE ships it?

Both approaches aren't mutually exclusive. Approach 1 could ship now, Approach 2 layered on when LE is ready.

Originally created by @zgv163 on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5479 **TL;DR:** There's no way to get valid TLS certificates for NetBird peer hostnames (e.g., `crm.netbird.cloud`). Tailscale solved this years ago with `tailscale cert`. Two viable paths exist: an internal CA (potentially via Smallstep), or the brand-new Let's Encrypt DNS-PERSIST-01 challenge type arriving Q2 2026. Is this on the roadmap? Would a community PR be welcome? --- ## The Gap When you access services over NetBird peer domains, browsers throw security warnings because there's no valid TLS cert for the hostname. WireGuard encrypts the tunnel, but browsers don't know that. The workarounds today aren't great: - Ignore the warnings (not acceptable when working in teams or production) - Set up a self-signed CA manually and install it on every device - Use the new Reverse Proxy, which is cool but always exposes things publicly, often the opposite of what you want This keeps coming up and there hasn't been an official response yet: - [[#2080](https://github.com/netbirdio/netbird/issues/2080)](https://github.com/netbirdio/netbird/issues/2080) - 22+ 👍, open since May 2024 - [[#4903](https://github.com/netbirdio/netbird/issues/4903)](https://github.com/netbirdio/netbird/issues/4903) - Dec 2025 - [[#5029](https://github.com/netbirdio/netbird/issues/5029)](https://github.com/netbirdio/netbird/issues/5029) - Jan 2026, directly references Tailscale ## Two Possible Approaches ### Approach 1: Internal CA The management server generates a root CA and signs certificates for peers on request. A `netbird cert` CLI command handles the flow. The peer's private key never leaves the device, only a CSR is sent. This could be built from scratch using Go's `crypto/x509` stdlib, or by integrating [[Smallstep's step-ca](https://github.com/smallstep/certificates)](https://github.com/smallstep/certificates) which brings ACME support, auto-renewal, and certificate policies out of the box. **Pro:** Works today, works for any domain including `.selfhosted`, `.local`, custom ones. **Con:** Users need to trust the CA on their devices. ### Approach 2: Let's Encrypt via [DNS-PERSIST-01](https://letsencrypt.org/2026/02/18/dns-persist-01) Let's Encrypt announced [DNS-PERSIST-01](https://letsencrypt.org/2026/02/18/dns-persist-01) in February 2026. It's a new ACME challenge where a single persistent DNS record authorizes an ACME account to issue certs for a domain and all its subdomains. No per-peer DNS updates needed, ever. ``` _validation-persist.netbird.cloud. IN TXT ( "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/XXX; policy=wildcard" ) ``` Set it once, issue certs for any `*.netbird.cloud` subdomain indefinitely. Production rollout is expected Q2 2026. **Pro:** Real publicly-trusted certs, zero trust store setup on client devices. **Con:** Only works for NetBird-controlled domains (cloud users) or self-hosters with a public domain. Depends on LE timeline. ## Where Should This Live? Should this be part of the **management server** (which already knows all peer identities and has gRPC channels to every peer), or within the **reverse proxy service** as an extension? Management feels like the natural home since this is about internal resources, but curious what the team thinks. ## The Ask 1. Is this planned? Even a rough timeframe helps the community plan around it. 2. Would a community PR for Approach 1 (internal CA) be welcome as a starting point? 3. For cloud users: could DNS-PERSIST-01 work with `netbird.cloud` once LE ships it? Both approaches aren't mutually exclusive. Approach 1 could ship now, Approach 2 layered on when LE is ready.

saavagebueno added the feature-request label 2026-08-05 01:29:59 -04:00

saavagebueno commented

2026-08-05 01:30:00 -04:00

@zgv163 commented on GitHub (Mar 6, 2026):

Revised direction: Let's Encrypt DNS-PERSIST-01

cc @mlsmaycon @pascal-fischer @braginini @lixmal

After prototyping the Internal CA approach (PR #5491, now closed), I concluded it's not viable cross-platform. iOS and Android can't programmatically trust a custom root CA. Tailscale reached the same conclusion (tailscale/tailscale#4454) and went with publicly-trusted Let's Encrypt certs instead.

What's changed: Let's Encrypt announced DNS-PERSIST-01 (staging late Q1, production Q2 2026). One persistent TXT record at _validation-persist.<domain> authorizes all future cert issuances, no per-request DNS changes. With policy=wildcard, a single record covers all peer FQDNs.

Looking at the codebase, there are two separate ACME implementations that don't share code: autocert for management and proxy, certmagic for Route53. The Go team has explicitly ruled out DNS challenge support for autocert (golang/go#23198), so dns-persist-01 can't be added there. On the other hand, lego already has a working dns-persist-01 implementation in v5 (#2871), written by an LE engineer.

A few questions:

Would consolidating ACME into a shared module backed by lego be of interest? It would unify cert handling for both management and proxy.
Would centralizing cert issuance on the management server make sense for proxied services too? Proxies wouldn't need internet-facing ACME ports anymore.
With dns-persist-01, the management server could issue publicly-trusted certs for peer FQDNs. Is this something the project would consider?

Happy to contribute a proof-of-concept if there's interest.

@zgv163 commented on GitHub (Mar 6, 2026): ## Revised direction: Let's Encrypt DNS-PERSIST-01 cc @mlsmaycon @pascal-fischer @braginini @lixmal After prototyping the Internal CA approach (PR #5491, now closed), I concluded it's not viable cross-platform. iOS and Android can't programmatically trust a custom root CA. Tailscale reached the same conclusion (tailscale/tailscale#4454) and went with publicly-trusted Let's Encrypt certs instead. **What's changed:** Let's Encrypt [announced DNS-PERSIST-01](https://letsencrypt.org/2026/02/18/dns-persist-01) (staging late Q1, production Q2 2026). One persistent TXT record at `_validation-persist.<domain>` authorizes all future cert issuances, no per-request DNS changes. With `policy=wildcard`, a single record covers all peer FQDNs. Looking at the codebase, there are two separate ACME implementations that don't share code: `autocert` for management and proxy, `certmagic` for Route53. The Go team has explicitly ruled out DNS challenge support for autocert ([golang/go#23198](https://github.com/golang/go/issues/23198)), so dns-persist-01 can't be added there. On the other hand, [lego](https://github.com/go-acme/lego) already has a working dns-persist-01 implementation in v5 ([#2871](https://github.com/go-acme/lego/pull/2871)), written by an LE engineer. A few questions: 1. Would consolidating ACME into a shared module backed by lego be of interest? It would unify cert handling for both management and proxy. 2. Would centralizing cert issuance on the management server make sense for proxied services too? Proxies wouldn't need internet-facing ACME ports anymore. 3. With dns-persist-01, the management server could issue publicly-trusted certs for peer FQDNs. Is this something the project would consider? Happy to contribute a proof-of-concept if there's interest.

saavagebueno commented

2026-08-05 01:30:00 -04:00

@renne commented on GitHub (Apr 11, 2026):

Suggested workflow:

Netbird peer creates Certificate-Sign-Request with own private key.
Netbird peer sends CSR to Netbird managment server
Netbird management server queries the DNS-PERSIST-01 record
Netbird management server requests the certificate from ACME-CA
Netbird management server sends the public certificate chain to Netbird peer.

The Netbird reverse proxy would just be a Netbird peer.

@renne commented on GitHub (Apr 11, 2026): Suggested workflow: 1. Netbird peer creates Certificate-Sign-Request with own private key. 2. Netbird peer sends CSR to Netbird managment server 3. Netbird management server queries the DNS-PERSIST-01 record 4. Netbird management server requests the certificate from ACME-CA 5. Netbird management server sends the public certificate chain to Netbird peer. The Netbird reverse proxy would just be a Netbird peer.

saavagebueno commented

2026-08-05 01:30:00 -04:00

@renne commented on GitHub (Apr 12, 2026):

Building on my previous comment: the workflow I described implies a broader architectural change worth naming explicitly — merging the Reverse Proxy into the Netbird client.

Current state:

netbird-proxy is a separate binary with its own lightweight WireGuard tunnel management
It is not a full Netbird peer; it needs a separate deployment (container, config, etc.)
netbird expose already added ephemeral per-peer proxying to the client itself

Proposed: Make the reverse proxy an optional capability of the regular Netbird client, activated via configuration or a flag (similar to how a peer opts into being a routing peer today). This means:

Any enrolled peer can act as a proxy node — no separate binary to deploy.
The peer already holds WireGuard tunnels to all other peers, so no duplicate tunnel infrastructure is needed.
Certificate delivery uses the DNS-PERSIST-01 workflow from my previous comment: the management server issues a publicly-trusted cert for the peer's FQDN and pushes it to the peer via the existing gRPC channel.
The peer serves HTTPS locally with that cert — without requiring internet exposure. Private services get trusted certificates purely within the overlay network.

This would directly solve the core problem in this issue: browsers warn because there's no trusted cert for peer.netbird.domain. With the client acting as proxy and receiving a cert from management, internal HTTPS "just works" on all platforms, including iOS and Android (publicly-trusted cert, no custom CA to install).

The netbird expose command is already a step in this direction (ephemeral, local ports). Making it permanent, cert-aware, and targeting remote peers/resources would complete the picture.

@renne commented on GitHub (Apr 12, 2026): Building on my previous comment: the workflow I described implies a broader architectural change worth naming explicitly — **merging the Reverse Proxy into the Netbird client**. **Current state:** - `netbird-proxy` is a separate binary with its own lightweight WireGuard tunnel management - It is not a full Netbird peer; it needs a separate deployment (container, config, etc.) - `netbird expose` already added ephemeral per-peer proxying to the client itself **Proposed:** Make the reverse proxy an optional capability of the regular Netbird client, activated via configuration or a flag (similar to how a peer opts into being a routing peer today). This means: 1. Any enrolled peer can act as a proxy node — no separate binary to deploy. 2. The peer already holds WireGuard tunnels to all other peers, so no duplicate tunnel infrastructure is needed. 3. Certificate delivery uses the DNS-PERSIST-01 workflow from my previous comment: the management server issues a publicly-trusted cert for the peer's FQDN and pushes it to the peer via the existing gRPC channel. 4. The peer serves HTTPS locally with that cert — **without requiring internet exposure**. Private services get trusted certificates purely within the overlay network. This would directly solve the core problem in this issue: browsers warn because there's no trusted cert for `peer.netbird.domain`. With the client acting as proxy and receiving a cert from management, internal HTTPS "just works" on all platforms, including iOS and Android (publicly-trusted cert, no custom CA to install). The `netbird expose` command is already a step in this direction (ephemeral, local ports). Making it permanent, cert-aware, and targeting remote peers/resources would complete the picture.

Sign in to join this conversation.

Branches Tags

main

claude/agent-network-test-cases-p743vw

android/gui-integration

revert/component-types

feat-post_quantum_ml_kem

ice-stun-wg-demux

dependabot/npm_and_yarn/proxy/web/npm_and_yarn-b39864987c

agent-network-setup-poc

dependabot/go_modules/aws-sdk-8f849ebaed

dependabot/github_actions/actions-a940c7c866

dependabot/go_modules/otel-e34c790afd

dependabot/go_modules/testcontainers-de325c0dd6

dependabot/go_modules/wireguard-dbd6b95108

dependabot/go_modules/pion-5f703e1eca

dependabot/go_modules/gorm-2271c8195b

fix-login-needed-check

dependabot/go_modules/google.golang.org/grpc-1.82.1

fix/ui-gtk3-support

enterprise-traefik-and-migration-fixes

disambiguate_p2p_metrics

revert/component-types-hookup

embedded-vnc

feature/ios-ssh

docs/agent-network-docs-update

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.106.3

dependabot/go_modules/github.com/pion/stun/v3-3.1.5

fix-ssh-authorized-users-multi-rule

peer-acl-multi-source

reverse-proxy-crowdsec-appsec

reverse-proxy-allow-match-or

client-local-metrics

lazy-conn-per-peer

lazy-conn-rosenpass

dependabot/go_modules/github.com/gopacket/gopacket-1.7.0

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.6

dependabot/go_modules/github.com/pires/go-proxyproto-0.15.0

dependabot/go_modules/github.com/jackc/pgx/v5-5.10.0

dependabot/go_modules/github.com/oapi-codegen/runtime-1.6.0

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.4

dependabot/go_modules/github.com/pkg/sftp-1.13.11

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.20.0

ssh-windows-privilege-check

fix/explicit-cors-handling

fix/remove-math-rand

test/gui-memory-leak-fix

fix/ui-status-dispatch

install-script-ui-dependencies

fix/grpc-get-network-map

fix/subscribe-status-coalesce

fix/tray-menu-item-leak

fix/windows-tray-race

feature/changeset

worktree-dns-route-qtype-fallthrough

mdm_integration

mlsmaycon-patch-2

feat/agent-network-ollama

proxy-tunnel-cache-ttl-env

coderabbitai/utg/1e5b0a5

grpc-acl

test/battery-drain

components-impl-drop-indexes-use-xids-no-resource-policy-map

fix/nmap-relevant-groups

e2e-guardrail-blocks-unselected-model

fix/lazyconn-cold-start-allowed-ips

vertex-guardrails-model-access-e2e

add-atomic-cache-ops

refactor/relay-foreign-cache

ci/trigger-release-tests

feature/kimi-3-agent-networks-dns-warmup

feature/dns-lazy-conn-warmup

daemon-ipc-acl

feature/ui-translation-key-parity-check

refactor/relay-foreign-cache-tests

fix/lazyconn-idle-keep-wg-peer

dmitri-propagate-auth-grant-types-on-combined

0.74.7-branch

diagnose-empty-vs-corrupt-state

windows-sleep-detector

fix/cli-up-wait-for-daemon

rp_key_persistency

feature/native-grpc

0.74.6-branch

0.74.6-branch-sync

0.74.5-branch-sync

0.74.4-branch

fix/remove-stale-peers-removal

fix/remove-stale-proxy-logic

fix/nsis-preserve-autostart-on-upgrade

refactor/peer-event-bus

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.3

dependabot/go_modules/github.com/pkg/sftp-1.13.10

components-impl-drop-indexes

fix-reset-aggregation-window-flake

dependabot/go_modules/github.com/pion/dtls/v3-3.1.5

0.74.x

fix/relay-states-lock

update-process-pkg

update-gopsutil-v4

fix/relay_states_lock

increase-sysinfo-timeout

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

dependabot/go_modules/github.com/eko/gocache/store/redis/v4-4.2.6

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.3

fix/fail-to-create-upnp-port-mapping-on-opnsense-firewall

0.74.3-branch

fix/routeselector-atomic-exit-node

netmap_progressive_alignment

nmap/components-impl

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

dependabot/go_modules/github.com/oapi-codegen/runtime-1.4.2

dependabot/go_modules/github.com/gopacket/gopacket-1.6.1

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.19.0

dependabot/go_modules/github.com/pires/go-proxyproto-0.12.0

fix/signal-watchdog-sync-stop

docs/agent-network

test/affected-logic

fix/revert-ice-filter

refactor/simplify-affected-peers

pascal-filter-policies-by-direction

claude/lock-contention-peer-connect-g8t6au

dmitri-filter-policies-by-direction

refactor/migrate-profiles-to-go

profile-bindings-ios

fix/skip-restart-unchanged-route

fix/mgmt-cache-async-resolve

refactor/wails-update-105

client_lifetime_serialization_refactor

fix/browser-ssh-2

fix/ipv6-and-netstack-accept-loop

fix/browser-ssh

profile-id-name-test

refactor/mgmt-bootstrap

feat/getting-started-unified-wizard

socket-grpc-permissions

fix/mysql-index-migration

windows-dns-firewall

tests/enable-race-on-tests

ui-refactor-gtk3

feature/affected-peers-grpc

profile-id

lazyconn-first-packet-fix-v2

claude/focused-gates-VMTgb

ui-tray-linux-leftclick

fix/ctx-enrichment

daemon-owner

feature/android-client-ssh

worktree-accept-ra-forwarding

nmap/combined-deploy

task/align_protobuff_toolset

feature/session-extend

add-json-yaml-flags

refactor/ephemeral-cleanup

claude/webtransport-relay-wasm-mUjY9

claude/vnc-udp-feasibility-6KB1U

fix/wgport-config

e2e-windows-dns-combined

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

release/0.68.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: DYNR/netbird#11544