Before you start
This is an administrator operation for a machine you are authorised to manage. The existing x86_64 Linux machine must have the supported hosting environment prepared. Obtain its verified SSH host fingerprint and private connection credentials through your approved secure process.
What to do
- Open Web nodes and choose Connect machine. Enter a recognisable node name, the SSH hostname or IP and the correct SSH port.
- Verify the host fingerprint directly with the machine owner before entering it. Enter the private key and its passphrase only in the trusted Nexus connection form; never paste them into Help, a support message or a public project description.
- Use Verify and connect, then inspect the accepted node and any error. Open Websites on that node to inspect its actual hosting inventory.
- Select the exact website before using its Node.js apps, Cron jobs, Commands or MCP controls. On an external node, Create website also requires the intended hosting account, domain and an IP configured on that machine.
- Use Disconnect management only when you intend to stop Nexus managing that external node. Reconnect management restores that management connection; inspect the current state before repeating an uncertain request.
What happens next
The connected node exposes its permitted website inventory and management controls. Disconnecting management is not a website-deletion or server-erasure workflow.
If something goes wrong
A fingerprint mismatch, unavailable SSH port or unprepared hosting environment must be resolved with the machine administrator. Do not bypass host verification or substitute another customer’s connection. Use the Operations result to distinguish a saved registration from a working connection.
