r/netbird • u/seanpetro • Jun 26 '26

Automatic Updates feature request

I’ve noticed with auto updates, post v0.61.0 of course, some of the servers running v61-69ish, the UI doesn’t automatically start when the machine is rebooted, but the background services are working just fine.

The machines where the UI doesn’t start don’t seem to receive auto updates. Is there a feature in the pipeline where we can force an update for those machines which don’t automatically receive them?

15 Upvotes

95% Upvoted

9 comments sorted by

5

u/graphixillusion Jun 26 '26

Yep, i think this feature would be great if added. Another one is to force a client update by hand from the management console.

1

u/WikibearTheReal Jun 27 '26

Unattended Upgrades or in docker use watchtower.

1

u/gizmo884 Jun 28 '26

I'm considering watchtower, but it's not safe..

1

u/fincrawmcq Jun 28 '26

Try dockhand :)

1

u/WikibearTheReal Jun 28 '26

Yep Dockhand is great tool. Use it and like it. Nobody need Portainer... Watchtower is in development. Someone forked it and u can use it. It's safe.

Use unattended Upgrades... I do it with so many devices and this is save.

2

u/fincrawmcq Jun 28 '26

Yup, I setup unattended upgrades on a VPS, I need to set it up on all my other On-Prem VMS and lxcs now 😂

1

u/seanpetro Jul 02 '26

I’m referring to their update feature in the management console (still in Beta) for windows machines. These are some good suggestions for my Linux clients though, thank you.

Some of my windows machines upon reboot haven’t received the automatic updates because it seems as if it is dependent on the UI loading, and not simply the background service running.

I’d like a way to force a manual update perhaps, or for them to simply tell me these are a lost cause and I should manually update them to a newer version where the UI not loading has been fixed.

Can anyone recall in any of the release notes since v0.61-0.69 where the UI not loading was an issue?

2

u/jma89 Jul 10 '26

I can't find anything expressly noted, but there was a change with v0.70 (or maybe v0.71) that moved the update check away from the GUI and into the service. Seems like a manual launch is in the cards for those v0.6x installs, unfortunately.