Your node keeps its enrollment when its hostname changes
TL;DR: A node's saved credentials were tied to its hostname, so a hostname change, common on Macs and DHCP networks, left the node unable to open them and sent it back to browser sign-in. Now they're tied to the machine's hardware ID instead.
Your node saves its credentials on disk, locked with a key made from the machine’s hardware ID and its hostname. On a Mac with no hostname set, and on machines whose network assigns the hostname, the hostname can change without you doing anything. When it did, the node couldn’t open its credentials at its next restart and quietly went back to asking you to sign in through the browser, so it looked like it had never been enrolled.
Now the key comes from the machine’s hardware ID alone, so a hostname change no longer locks your node out of its own credentials.
What changes
- A node that can’t open its credentials says so. It logs an error, and suggests checking the hostname when that’s the likely cause, instead of looking like a node that never enrolled.
- Credentials still open only on the machine they were made on. A copy of the files doesn’t open on another machine.
- Rolling back still works. The node keeps its old copy of the credentials beside the new one, so an older version can still read them.
Limits
- A node whose hostname has already changed has to get its old hostname back once, before or after updating. On macOS, that’s
sudo scutil --set HostName <old name>. Once the updated node has opened its credentials, the hostname no longer matters. - On a system with no hardware ID, the hostname is still part of the key, as before.
What you need to do
Update your node to v0.0.134 or later. If it has already lost its enrollment after a hostname change, set the old hostname back first.