If you deployed your Cloud Server with an SSH key, you can connect without using a password. This is typically the quickest and most secure way to access a new server.


This guide covers how to connect from Windows, Linux, and macOS using the SSH key you selected during deployment.

For SSH key creation instructions and how to configure your SSH key for use within BinaryLane, please see: Set a default SSH key for all new Cloud Server installations

TABLE OF CONTENTS


Windows


Recent versions of Windows include the OpenSSH client, which can be used from PowerShell, Command Prompt, or Windows Terminal.


To connect using the default SSH key already loaded from your user profile, run:

ssh root@YOUR_SERVER_IP


If your private key is stored in a non-default location, specify it directly:

ssh -i C:\Users\YOUR_USERNAME\.ssh\id_ed25519 root@YOUR_SERVER_IP


The first time you connect, Windows will ask you to confirm the server's host key fingerprint. This is expected for a new server.


If you prefer PuTTY, see also:


Optional advanced setup
If you would like a faster one-command workflow on Windows, you can use the expandable section below to set up a local sshbl shortcut.


Show Windows sshbl setup steps


If you regularly connect to BinaryLane servers using the same SSH key, you can create a simple PowerShell shortcut so you can run commands such as:

sshbl root@YOUR_SERVER_IP


Step 1: Open PowerShell and create your PowerShell profile if it does not already exist:

if (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force }
notepad $PROFILE


Step 2: Add the following function to the profile file:

function sshbl {
    param(
        [Parameter(ValueFromRemainingArguments = $true)]
        [string[]]$Args
    )

    ssh -i "$HOME\.ssh\id_ed25519" @Args
}


Step 3: Save the file, close PowerShell, and open a new PowerShell or Windows Terminal session.


Step 4: Connect using:

sshbl root@YOUR_SERVER_IP


Notes
- This is a local shortcut on your Windows device.
- Update the key path if your private key uses a different filename or location.
- These instructions assume you are using the Windows OpenSSH client and an OpenSSH-format private key.


Linux


Most Linux distributions already include the OpenSSH client.


To connect using your default SSH key:

ssh root@YOUR_SERVER_IP


If you need to specify a particular key:

ssh -i ~/.ssh/id_ed25519 root@YOUR_SERVER_IP


If your server was provisioned with a different username, replace root with that user.


macOS


macOS includes the OpenSSH client in the Terminal application.


To connect using your default SSH key:

ssh root@YOUR_SERVER_IP


If you need to specify a particular key:

ssh -i ~/.ssh/id_ed25519 root@YOUR_SERVER_IP


The first time you connect, you may be asked to confirm the server fingerprint. Type yes to continue if the details are correct.


Troubleshooting


  • Permission denied (publickey)
    Make sure you are using the correct private key for the public key that was deployed to the server.
  • Wrong username
    Some server images or cloud-init setups use a non-root account. Try the user you created during setup if root does not work.
  • Connection timed out
    Confirm the server is online, the IP address is correct, and any firewall rules allow SSH access on port 22.
  • Key not found automatically
    Use the -i option to point SSH to the correct private key file.


Related articles:


If you need assistance, submit a ticket.