Skip to navigation

SSH Keys

An SSH key is a pair of matching files that lets you log in to a Linux VM without typing a password. The public key goes on the VM; the private key stays on your computer and proves it’s you. Think of the public key as a lock you fit on the server and the private key as the only key that opens it.

You save public keys in the portal once, then pick them when you deploy a VM. IBEE puts the selected public keys on the VM when it is created.

Choose how to log in

Your VMLog in withNotes
Linux, from your computerSSH key (recommended)Can’t be guessed like a password. Required if you turn password login off.
Linux, no key at handPassword loginSet or reset under the VM’s Settings → Access. Turn it off once a key works.
WindowsRemote Desktop (RDP, port 3389) as AdministratorSSH keys aren’t used: the deploy form hides the SSH Keys section for Windows images.

Saved SSH keys are personal: the list shows the keys you saved in the current workspace. Teammates don’t see your keys, and you don’t see theirs.

How it works

  1. You create a key pair in the portal (it downloads the private key), or you import the public key of a pair you already have.
  2. When you deploy a Linux VM, you select one or more saved keys.
  3. You connect with ssh and your private key.

Before you begin

  • Write access to the workspace: the Owner, an Admin, or a Technical member with access to it. Collaborators can only view. See Team members & access roles.
  • Identity verification, to create, import or delete keys. See Verify your identity.
  • To import a key: the public key file from your computer, usually ~/.ssh/id_ed25519.pub. Never upload the private key.
  • An SSH client. macOS, Linux and Windows 10 or later include ssh in the terminal.

Create a key pair in the portal

Use this when you don’t have a key yet.

1

Open SSH Keys

Open a workspace. In the sidebar, under Tools, click SSH Keys.

2

Start a key pair

Click Create Key Pair. The Add SSH Key dialog opens.

3

Name the key

Enter a Key Pair Name that says where the key lives, for example my-laptop (up to 100 characters). Add a Description if you like (optional, up to 500 characters).

4

Create and download

Click Create & Download. The portal shows “Key pair created. Private key downloaded once.” and your browser downloads the private key as my-laptop.pem. The key appears in the list with Key Type ssh-ed25519.

The private key downloads once only. IBEE keeps only the public key and can’t send the private key again. Move the .pem file somewhere safe now. If you lose it, create a new key pair and add it to your VMs.

ssh refuses a private key that other users on your computer can read. On macOS or Linux, lock it down after downloading:

mkdir -p ~/.ssh
mv ~/Downloads/my-laptop.pem ~/.ssh/
chmod 600 ~/.ssh/my-laptop.pem

Import a key you already have

To make a new key pair on your own computer first, run this and press Enter at each prompt:

ssh-keygen -t ed25519 -C "you@example.com"

This creates ~/.ssh/id_ed25519 (private, keep it) and ~/.ssh/id_ed25519.pub (public, import this one).

1

Start the import

On SSH Keys, click Import Key.

2

Name the key

Enter a Key Pair Name and, optionally, a Description.

3

Add the public key

Paste the key into Public Key, or click Choose public key file and pick the .pub file. A public key is one line that starts with its type, such as ssh-ed25519 AAAA…, ssh-rsa AAAA… or ecdsa-sha2-nistp256 AAAA…. A PEM file that contains a PUBLIC KEY also works.

4

Import it

Click Import Key. The portal shows “SSH public key imported” and the key appears in the list.

Use a key when you deploy a VM

In the VM deploy form, select one or more saved keys in the SSH Keys section, or click Add Key to create or import one without leaving the form. See Create a VM.

Through the API, saved keys have no endpoints of their own: send the public key text in ssh_keys when you create a VM. See Create a VM.

Connect to the VM

On the VM’s Overview, Connection Details shows its IP address and login user. Connect with the matching private key:

# Key pair created in the portal
ssh -i ~/.ssh/my-laptop.pem <user>@<vm-ip>
# Key you created with ssh-keygen
ssh -i ~/.ssh/id_ed25519 <user>@<vm-ip>

Verify it worked

The first time, ssh asks you to confirm the server’s fingerprint: type yes. You then get a shell prompt on the VM without being asked for a password.

Add or remove keys on a running VM

Open a running Linux Cloud or GPU VM and go to Settings → Access. You need write access to the workspace.

  • SSH keys lists the keys installed on the VM. To add one, pick a saved key in Select SSH key and click Add key. Tick Disable password login after adding this key to switch to key-only login at the same time.
  • Click Remove to take a key off the VM. If password login is off, removing the last key asks Remove the last SSH key?: confirm with Remove key only if you have another way in.
  • Password login shows On or Off; click Turn on or Turn off. You can turn it off only while the VM has at least one SSH key.
  • Reset password: enter a New password (at least 8 characters) twice and click Reset password.

Windows VMs show a Remote Desktop section instead; manage users and passwords inside Windows.

Through the API, use PATCH /compute/cloud-vms/{vm_id}/actions/access (GPU VMs: /compute/gpu-vms/{vm_id}/actions/access) with ssh_keys and ssh_key_mode (add or remove), new_password, or password_auth_enabled.

Delete a saved key

On SSH Keys, click Delete on the key’s row, then Delete Key in Delete SSH Key.

Deleting a saved key only removes it from your list. It does not take the key off VMs that already have it, even though the dialog says servers will stop accepting it. To cut off access, remove the key from each VM under Settings → Access, or delete its line from ~/.ssh/authorized_keys on the VM.

Limits

Value
Key generated by Create Key Paired25519, private key in OpenSSH format, downloaded once as <name>.pem
Key types you can importRSA, DSA, ed25519, ECDSA (256, 384, 521), security-key (sk-…) and certificate (…-cert-v01) keys, and PEM public keys
Public key file sizeUnder 64 KB
Key Pair Name1–100 characters, unique across all your saved keys (not case-sensitive)
DescriptionUp to 500 characters
Same public keyCan be saved once per person, in one workspace
Who sees a keyOnly the person who saved it
Password after resetAt least 8 characters

Because each person can save a public key only once, you can’t save the same key in a second workspace. Create a separate key pair for each workspace, or pass the public key text in ssh_keys through the API.

Security tips

  • Use one key pair per computer, so you can remove one laptop’s access without touching the others.
  • Protect the private key with a passphrase when you run ssh-keygen.
  • Once a key works, turn Password login off under Settings → Access.
  • When someone leaves your team, remove their keys from each VM under Settings → Access.

Troubleshooting

You seeWhat it meansWhat to do
”Private key files cannot be imported. Select the matching .pub or PEM public-key file.”You pasted or picked the private keyImport the .pub file instead
”Use a supported one-line OpenSSH key or a PEM file containing a public key.”The text isn’t a public keyCopy the whole single line of the .pub file
”SSH public key files must be smaller than 64 KB”The file is too big to be a public keyPick the .pub file
”A key with this name already exists.”A key in your list already uses the nameChoose another name
”SSH key import failed” or “SSH key creation failed”You already saved a key with this name or this exact public key, in this or another workspaceUse a new name, or a new key pair
My key isn’t offered in the deploy formYou are in a different workspace, or a teammate saved the keyDeploy in the workspace where you saved it, or import your own key here
Permission denied (publickey)The VM doesn’t have the matching public key, or the user is wrongCheck the user in Connection Details, pass the right file with -i, and check the key is listed under Settings → Access
WARNING: UNPROTECTED PRIVATE KEY FILE!The private key file can be read by othersRun chmod 600 on it
Connection timed outThe VM is stopped, or a firewall blocks port 22Start the VM and allow TCP port 22 from your IP address in its firewall group
The .pem file is lostIt can’t be downloaded againCreate a new key pair and add it under Settings → Access