GigakubeWikigigakube.ch →Menu ↓

SSH keys

The keys you use to get into your servers: you save them once in your account and choose them each time you create a server.

Why you need them

Server images have no password: you get in with SSH and a key. You give us the public part of the key; the private part stays on your computer and you never give it to anyone.

Keys belong to your account, not to a project: you see and use them in all your projects.

Creating a key on your computer

If you do not already have one (usually in ~/.ssh/id_ed25519.pub):

ssh-keygen -t ed25519 -C "me@laptop"
cat ~/.ssh/id_ed25519.pub

The last line prints the public key, which starts with ssh-ed25519 AAAA…. That is the one to copy. On Windows the same command works in PowerShell.

Accepted types: ssh-ed25519 (recommended), ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521. Old ssh-dss keys are not accepted.

Saving it in the panel

SSH Keys menu → + Add SSH Key:

  1. Key name: a name that tells you which computer it is from (for example Office laptop);
  2. Public key: paste the whole public key;
  3. Add key.

In the list you see name, fingerprint (FINGERPRINT) and date. You can Rename and Delete. Up to 20 keys; names are unique, and the same key cannot be saved twice.

Using it

When creating a server, in SSH key, choose the saved key (or paste one on the spot). The key is added to the image's default user, for example ubuntu. Then: Connecting with SSH.

Good to know:

For developers

With an API key: SshKey/getList (operator role) returns the saved keys with their uuid; SshKey/create, update, delete need an admin key. When creating a server you use a saved key with ssh_key_uuid (/api/rpc only), or pass the whole public key in ssh_key (API and MCP).