Connecting to your server over SSH

SSH (Secure Shell) is the encrypted connection you use to administer a Linux server from your computer. Key-based sign-in is both more secure and more convenient than typing a password.

Create an SSH key

On macOS, Linux or Windows 10 and later, open a terminal (on Windows, use PowerShell) and run:

ssh-keygen -t ed25519 -C "[email protected]"

Accept the default location and set a passphrase when asked. This creates two files: a private key (id_ed25519), which never leaves your computer, and a public key (id_ed25519.pub), which you give to the server. Display the public key with:

cat ~/.ssh/id_ed25519.pub

Paste the whole line into SSH public key when you deploy the server. If the server already exists, open a ticket with the public key and our team can add it.

Find your access details

When the server is Active, its page shows Access details: the public IP, SSH host, SSH username and SSH port, each with a copy button. The Root password stays hidden until you choose Reveal. Reveals are limited and recorded for security, so store the password in a password manager rather than revealing it each time.

Sign in

Using the values from the page:

ssh [email protected]
ssh -p 2222 [email protected]

Use the second form when the page shows a port other than 22, and replace root if a different username is shown. The first time you connect, confirm the host fingerprint by typing yes.

Essential first-hour hardening

On an Ubuntu or Debian server, a sensible starting point is:

1. Install updates: apt update && apt upgrade -y
2. Create an administrator account and use it instead of root:

   adduser deploy
   usermod -aG sudo deploy
   rsync --archive --chown=deploy:deploy ~/.ssh /home/deploy

3. Enable a firewall that allows SSH before anything else:

   ufw allow OpenSSH
   ufw allow 80,443/tcp
   ufw enable

4. Disable password and root sign-in once key sign-in for your new user works: in /etc/ssh/sshd_config set PasswordAuthentication no and PermitRootLogin no, then run systemctl reload ssh.

Keep your current session open while testing a new sign-in in a second window. That way, a configuration mistake cannot lock you out. On AlmaLinux or Rocky Linux, use dnf for updates and firewalld for the firewall.

If you are locked out

Open a High priority ticket from your account with the server hostname and what changed. Our team can help you regain access.