Engine.Start receives the login response's NetbirdConfig but only runs it
through PopulateNetbirdConfig, so handleDebugUploadUpdate never saw it: the
destination the management server publishes reached the engine only on the
first sync afterwards. A debug bundle requested in that window resolved no
published destination and fell back to the service NetBird runs, even on a
deployment that had configured its own — the opposite of what configuring it
is for.
Seen with a remote job triggered shortly after the peer reconnected: the job
succeeded against NetBird's upload service while the account setting named a
different host.
riccardom
a8ba9d0149