netbirdio
Auto-Update functionality for netbird client
Is your feature request related to a problem? Please describe. Client Updates are currently manual.
Describe the solution you'd like It would be great if the netbird client had an auto update function. Users who don't want to should be able to disable it and update the client manually with a button in the client settings.
yes this feature would be super nice because if you have like 100 peers the update stuff is very nasty especially on clients with users.
if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?
if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?
yes for linux thats works but in Windows you have to do it manually. Another point from my experience client user never click on update if the admin doesnt advise to do it so a "force" update button for the admin would be awesome maybe with a option to force update on the whole linux client (apt upgrade ...)
if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?
MacOS - I don't know if netbird would like to enter the Mac App Store... An auto-update of just the client would also be useful for Linux systems which are used for subnet routing.
auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not.
auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not.
Of course, the auto-update functionality should be an optional feature.
+1 From our side as well. It is now a nightmare to manage. If at least the Windows client would trigger/ask users to update to new version that would help enormously already.
auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not.
From an Enterprise perspective, being able to push upgrades from the management console to a given machine, or group of machines, to a specified version (meaning that we can run a couple of versions behind release if desired, for example), would be a great feature to have.
By groups of machines, I mean being able to allocate upgrades to machines:
- in a specific network, or
- currently running a specific version or
- currently running a version older than a given release, or
- machines matching a given tag within Netbird (a basic tagging API would probably be a prerequisite for this - did I miss one? There doesn't seem to be one referred to in the API docs, at a glance.)
Hi, Is this feature planned for release, or will it not be implemented? We have over 100 users, and doing manual updates is quite a pain.
I've been testing NetBird for a couple of months on the side really, and I love it, but the lack of any sort of automatic or remote update is going to prevent me going any further at this time - I'm sure it'll come and when it does I'll be back 💯 Keep up the great work!
I feel there were 3 Updates in the last week. Auto-Update is so needed. Thanks
For Windows would suggest an Upgrade Helper Service which should be part of the Client's automatic update process.
A service that monitors and attempts to reinstall the client if an upgrade fails, such as during a system restart or failed upgrade to rollback.
Just in case it helps someone while a native auto-update is being discussed here:
I’ve published a small set of helper scripts that implement delayed / staged auto-updates for NetBird on the client side (Windows, macOS, Linux). They don’t depend on the NetBird dashboard and are built around the OS package managers / installers:
Key ideas:
- no auto-install (only upgrade if NetBird is already present),
- new versions must “age” N days before being installed (to avoid short-lived/broken releases),
- daily scheduled checks (Task Scheduler / systemd timer / launchd),
- logs and simple local state (JSON) on each machine.
These are not a replacement for a first-class auto-update feature in NetBird itself, but they’ve been useful to keep clients reasonably up to date with some safety margin.
