[GH-ISSUE #4139] Docs of client config file #8778

Open
opened 2026-08-05 01:19:31 -04:00 by saavagebueno · 4 comments
Owner

Originally created by @karlveezoo on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4139

Is your feature request related to a problem? Please describe.
Is there any docs for the client configuration file? I see it is mentioned you can use a client configuration file, but can't find much info on what to put there. I would like my client to do "block inbounds connections" automatically for example without having to add it as an cli option every time you do "netbird up"

Describe the solution you'd like
Introduce docs for client config file, or if there already is, link it more clearly in the docs

Describe alternatives you've considered
N/A

Additional context
N/A

Originally created by @karlveezoo on GitHub (Jul 11, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4139 **Is your feature request related to a problem? Please describe.** Is there any docs for the client configuration file? I see it is mentioned you can use a client configuration file, but can't find much info on what to put there. I would like my client to do "block inbounds connections" automatically for example without having to add it as an cli option every time you do "netbird up" **Describe the solution you'd like** Introduce docs for client config file, or if there already is, link it more clearly in the docs **Describe alternatives you've considered** N/A **Additional context** N/A
saavagebueno added the feature-request label 2026-08-05 01:19:31 -04:00
Author
Owner

@nazarewk commented on GitHub (Jul 11, 2025):

The client.json configuration file is mostly an internal JSON dump of this struct if I'm not mistaken. It is possible to edit it manually while the client daemon is down, but it is generally not expected to be manually edited by users and to use netbird up or other flags to configure.

<!-- gh-comment-id:3061188505 --> @nazarewk commented on GitHub (Jul 11, 2025): The `client.json` configuration file is mostly an internal JSON dump of [this struct](https://github.com/netbirdio/netbird/blob/7f1d25937cfbdb3ca8ec5b4b5ac8bf1bc198e605/client/internal/config.go#L82-L145) if I'm not mistaken. It is possible to edit it manually while the client daemon is down, but it is generally not expected to be manually edited by users and to use `netbird up` or other flags to configure.
Author
Owner

@karlveezoo commented on GitHub (Jul 11, 2025):

Could we make it possible to use environment variables for settings like block inbounds connections etc? I would like for users to be able to configure this in their .bashrc for example so it a default settings when running netbird

<!-- gh-comment-id:3061318615 --> @karlveezoo commented on GitHub (Jul 11, 2025): Could we make it possible to use environment variables for settings like block inbounds connections etc? I would like for users to be able to configure this in their .bashrc for example so it a default settings when running netbird
Author
Owner

@nazarewk commented on GitHub (Jul 11, 2025):

We will very likely tackle the unification of the NetBird client configuration modes (there are WAY too many right now) before releasing 1.0, but it's very hard to estimate a timeline for this.

The --block-inbound itself is a flag on netbird up. It should be remembered after you set it once. Alternatively you can to set NB_BLOCK_INBOUND envvar to have it forced netbird up command.

The root and up command flags all can be set by 1) replacing - with _ 2) uppercasing 3) prefixing with NB_.

<!-- gh-comment-id:3061595224 --> @nazarewk commented on GitHub (Jul 11, 2025): We will very likely tackle the unification of the NetBird client configuration modes (there are WAY too many right now) before releasing `1.0`, but it's very hard to estimate a timeline for this. The `--block-inbound` itself is a flag on `netbird up`. It should be remembered after you set it once. Alternatively you can to set `NB_BLOCK_INBOUND` envvar to have it forced `netbird up` command. The root and `up` command flags all can be set by 1) replacing `-` with `_` 2) uppercasing 3) prefixing with `NB_`.
Author
Owner

@karlveezoo commented on GitHub (Jul 11, 2025):

Thanks, good enough for me. It might be that I haven't looked around enough in the docs, but otherwise it would be good to document it a bit more thoroughly.

Feel free to close this one if this is already tracked for the 1.0 release

<!-- gh-comment-id:3061621727 --> @karlveezoo commented on GitHub (Jul 11, 2025): Thanks, good enough for me. It might be that I haven't looked around enough in the docs, but otherwise it would be good to document it a bit more thoroughly. Feel free to close this one if this is already tracked for the 1.0 release
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#8778