Connect a node

A node is your machine running the Nexardo agent. The agent installs, starts, and performs other authorized operations on games. Enrollment begins in your organization's Providers settings.

Check the requirements

Use a supported Linux server with internet connectivity, SSH access, and sudo privileges. Manual enrollment offers Linux amd64/arm64 builds; check the game's architecture compatibility separately. Windows is not a verified game lifecycle platform yet.

The API address must be reachable from the target machine. On a VPS, localhost means that VPS, not the computer running your Nexardo dashboard.

Install the agent yourself

1. Select your organization and open Providers. Start machine enrollment under the appropriate provider.
2. Choose Install myself, then Continue.
3. Copy the installation command from the wizard and run it over SSH on the target machine.
4. Copy the one-time token and paste it into the hidden terminal prompt. Invisible input is expected.
5. Wait for registration. The wizard updates the node state automatically.

Use the current command from the dashboard: it contains your connection's API address and installation parameters. A sample command with a fictional token cannot register your node.

Connect over SSH

The wizard also offers Connect over SSH. It asks for the machine address, user, authentication method, sudo configuration, server key fingerprint, and your account password for confirmation.

Verify the fingerprint against a trusted source from your provider or the machine itself. Do not accept an unknown fingerprint simply to proceed. Follow the connection result in the same wizard.

Review discovered games

After registration, the agent discovers existing servers. Check the root directory and data paths for each candidate. Verify a candidate before adopting it. If nothing is found, continue deploying a new game service.

Discovery searches and checks paths; it does not establish that all game data is safe. Back up your world and configuration before adopting an existing game.

If the node does not connect

• Confirm that you used the correct machine and the token has not expired.
• Check outbound access to the API address; replace an incorrect localhost value.
• Inspect the wizard's error message and installation log.
• Avoid running multiple installations at once.

After registration, continue with your first server. See Monitoring and troubleshooting for the general diagnostic sequence.