Adding a Server

How to add an SSH host in VybeCoding, hostname, port, username, password vs SSH key authentication, key generation, and key import on iOS.

Every SSH connection in VybeCoding starts with adding a server to your host list. You need the hostname or IP address of the machine, the SSH port, a username, and a way to authenticate, either a password or an SSH key. This guide walks through both methods and explains how to generate and import SSH keys on iOS.

Adding a Server with Password Authentication

Tap the plus button on the main screen. Enter the hostname or IP address, this can be a local IP like 192.168.1.50, a public IP, a Tailscale IP like 100.x.y.z, or a domain name. The default SSH port is 22; change it only if your server uses a non standard port. Enter your username (the account you log into on the server) and your password. Tap Save, then tap the server to connect. VybeCoding stores credentials securely in the iOS Keychain.

warningPassword authentication is convenient but less secure than SSH keys. If your server is exposed to the internet, passwords can be brute-forced. Switch to key-based authentication as soon as possible and disable password auth on your server.

Understanding SSH Keys

SSH keys are a pair of cryptographic keys, a private key that stays on your device and a public key that goes on the server. When you connect, the server challenges your device to prove it holds the private key without ever transmitting it. This is fundamentally more secure than passwords because the private key never leaves your device, the key is too long to brute-force, and you can revoke access by removing the public key from the server without changing any passwords.

Generating an SSH Key

The recommended key type is Ed25519, it is fast, secure, and produces short keys. You can generate a key pair on any machine with OpenSSH installed. Run the following command on your Mac, Linux box, or even on a server you already have access to. When prompted, set a passphrase for extra security or leave it empty for convenience.

bash

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

Installing the Public Key on Your Server

Once you have a key pair, the public key (the file ending in .pub) needs to be added to the server. The easiest way is with ssh-copy-id, which appends your public key to the server's authorized_keys file automatically. After running this command, the server will accept connections from any device holding the corresponding private key.

tipIf ssh-copy-id is not available, you can manually append the contents of your .pub file to ~/.ssh/authorized_keys on the server. Make sure the .ssh directory has permissions 700 and the authorized_keys file has permissions 600.

bash

ssh-copy-id -i ~/.ssh/id_ed25519.pub user@your-server

Importing a Private Key into VybeCoding on iOS

To use key authentication on your iPhone, you need to get the private key file onto the device and import it into VybeCoding. You can AirDrop the private key file from your Mac, email it to yourself and open it in VybeCoding, save it to iCloud Drive or Files and open it from there, or paste the key contents directly in the VybeCoding host configuration. When adding or editing a server in VybeCoding, select Key as the authentication method. Tap Import Key and choose your private key file, or paste the key text directly. VybeCoding supports Ed25519, RSA, and ECDSA key formats. The key is stored in the iOS Keychain and never leaves your device.

warningNever share your private key publicly or commit it to a git repository. The private key is like a master password, anyone who has it can access your servers. Delete the key from email or messaging apps after importing it.

Disabling Password Authentication on the Server

Once key authentication is working, you should disable password login on the server to prevent brute-force attacks. Edit the SSH server configuration file and restart the SSH service. After this change, only devices with an authorized key can connect.

/etc/ssh/sshd_config

# Edit SSH config
sudo nano /etc/ssh/sshd_config

# Set these values:
# PasswordAuthentication no
# PubkeyAuthentication yes

# Restart SSH
sudo systemctl restart sshd