Why does orbit daemon stop when I publish an orbit update on my update server? or is it needed to be updated when hosts are offline? since the autoupdate server works for Osquery and I can upgrade or downgrade the version of osquery but I can't do the same for orbit since it kills the daemon and how to avoid the

--insecure

flag?

As mentioned in the other thread, self-hosted updates are a premium feature that may only be used by those with a paid Fleet Premium license. Support for the self-hosted update tooling is available to paid users via the private Slack support channels.