Add a Server

Open Servers → New Server and fill in:

• Name: shown when you pick a server for a project, for example Tokyo 4C 8GB.
• Public IP or hostname and SSH port (usually 22).
• SSH user: root, or a user with passwordless sudo. Cloud images often disable root login; use ubuntu on Ubuntu images, debian on Debian, ec2-user on Amazon Linux.
• Authentication:
  • Password: used once to install a key that only Zenavo holds. The password is not stored.
  • Private key: upload the key file or paste it. It must be an unencrypted OpenSSH or PEM private key, not the .pub file. If it has a passphrase, remove it with ssh-keygen -p -f <file>. The key is stored encrypted.

Finding the key file

Keys usually live in ~/.ssh, which file pickers hide. Press ⌘ ⇧ G in the macOS file picker and type the path, or ⌘ ⇧ . to show hidden folders.

Click Connect and set up. Zenavo:

1. Connects over SSH and shows the server's host key fingerprint. Zenavo checks this fingerprint on every later connection and refuses to connect if it changes.
2. Checks the operating system, CPU, memory and sudo access.
3. Installs a pinned version of K3s, then cert-manager with a Let's Encrypt issuer.
4. Verifies that the node, Traefik, the storage provisioner and metrics are ready.

Progress is shown live on the server's Status tab. If setup fails, fix the reason shown and click Run setup under Settings; finished steps are skipped.

Check the host key

To make sure you connected to the right machine, compare the fingerprint the console shows with the one on the server:

ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub

On most clouds you can also read it from the instance's serial console without SSH.