Describe the problem
I’m new to netbird.
I set up a netbird server with a reverse proxy, added an A record and a wildcard CNAME record. Pretty standard. When setting up my first service, I wanted to restrict it to netbird only, but this wasn’t an option, because the reverse proxy running on my server doesn’t “report the Private capability”. A little perplexed, I created another cluster and launched a proxy using Docker. This proxy lets me both expose things to the internet as well as restrict access to netbird only.
I noticed that this second proxy had an env var set: “NB_PROXY_PRIVATE=true”. I’m struggling to understand why the “default” reverse proxy doesn’t also have that env var set. I added it in docker-compose.yml and it seems to work as expected, but I feel like there must be a reason why it’s not enabled by default.
Expected behavior
I expected to be able to use netbird-only access using the reverse proxy running on my newly created netbird server.
Are you using NetBird Cloud?
Self-hosted.
NetBird version
Management v0.75.0
Dashboard v2.90.7