NodePilot Onboarding
NodePilot connects directly to Windows and Linux systems over SSH. The onboarding process creates the connection, authorises NodePilot's SSH key and verifies that the host is ready to use.
1.Add a host
Open NodePilot and tap + Add host. Enter a name for the system and its hostname or IP address.
Enter the SSH username and port. The default SSH port is 22.
2.Check the host
Use Check Host. NodePilot will try to reach the system and detect whether it is running Windows or Linux.
If available, NodePilot can also detect network information used for Wake-on-LAN, such as the MAC address and broadcast address. These values remain editable.
3.Authorise NodePilot
Open Authorize NodePilot. NodePilot provides its public SSH key and a command that can be copied to the target system.
Run the command on the host using the same account that NodePilot will use for SSH access.
4.Windows permissions
For Windows hosts, install the SSH key for an account that has the permissions required for the actions you want to use.
A standard Windows account may be able to log in through SSH while still being prevented from performing remote power or administrative actions. For the most complete NodePilot functionality, use an appropriate local administrator account where your environment permits it.
If Windows blocks an action, NodePilot will report that elevated rights are required.
5.Verify the connection
Return to NodePilot and run the connection check again. A successful SSH check confirms that the host is authorised and reachable.
Save the host. It will now appear in the NodePilot host list.
6.Start using NodePilot
Open the host to see the actions available for that system. Depending on the platform and permissions, NodePilot can provide system insights, Wake-on-LAN and guarded power controls such as restart and shutdown.
If a host is offline, Wake-on-LAN remains available when it has been configured correctly.
Troubleshooting
Host cannot be reached
Check the hostname or IP address, SSH port, local network or VPN connection, and make sure the SSH server is running on the target system.
SSH works, but an action is blocked
This usually indicates a permissions issue on the target system rather than a connection problem. On Windows in particular, remote administrative actions can require elevated rights.
Wake-on-LAN does not work
Verify the MAC address and broadcast address and make sure Wake-on-LAN is enabled in the target system's firmware, network adapter settings and operating system configuration.