Repoint a node
Change the server address or credential stored by an enrolled node.
Before you start
Use this when your server moves to a different address or you need to store a rotated node key. The node keeps its ID and the server signing key it already trusts.
Automatic LAN connections
A paired node checks for a faster direct connection when it starts or reconnects. It verifies that each address belongs to the control plane it already trusts, and keeps your configured server address as the fallback. Previously verified address hints let it try the LAN even when the public address is unavailable.
Selection currently covers private IPv4 and mesh addresses. The node keeps a healthy connection in place; it doesn't reconnect just to switch routes. Its log reports the selected address and probe time. The browser continues using the address you opened, so its OAuth callback doesn't change.
Both the server and node need versions that support discovery. Older servers continue to use the configured address.
Change the address
subshell configure --server https://server.example.comReplace the example URL with your server's new address. A running daemon reloads valid connection settings on its next heartbeat and reconnects automatically. Terminal streams can briefly disconnect while it reconnects. If the daemon is stopped, start it through its service or the terminal where you normally run it.
Changing the server URL clears the saved WebSocket address so the node can discover where to connect.
Recover node credentials
The node page offers Re-register to generate a setup key tied to the existing node. Follow Re-register an existing node to apply it with Subshell Client while preserving the node entry.
Store a rotated key
If you obtained a rotated node credential through the API, store it on that machine:
subshell configure --key REPLACE_WITH_ROTATED_NODE_KEYA running daemon reloads the credential and reconnects automatically. A setup key beginning with nsk_ isn't a rotated node key; it belongs to setup or enroll.
Change control planes
Changing the address doesn't change which server signing key the node trusts. To join a different instance, stop and unenroll the node, then enroll with the new instance's setup key.
Next steps
See Unenroll a node and Enroll a node with the CLI.
Edit on GitHubLast updated on
