How to Connect to Your VPS With SSH on Windows

SSH (Secure Shell) gives you an encrypted command line on your VPS, so you can manage it from your own computer. Windows 10 (version 1809 or later) and Windows 11 include an SSH client, so you don’t need to install another program.

Before you start

• Have the login details we gave you when your server was set up: the server’s IP address, the username and the SSH port (a port is a numbered door on the server). If no port is listed, use the standard port 22. If you don’t have these details, open a support ticket.
• The examples below use the documentation address 203.0.113.10. Replace it with your own IP address, and replace username with your username.

Step 1: Open PowerShell and check for SSH

1. Select Start, type PowerShell and open Windows PowerShell.
2. Type ssh and press Enter.
3. If you see a few lines starting with usage: ssh, the SSH client is installed. That isn’t an error. Go to step 2.
4. If Windows says ssh is not recognized, add the client. You need a Windows account with administrator rights for this; if you don’t have one, ask whoever manages your computer.
   1. Select Start, type Optional features and open Optional features (on Windows 10 it may be called Manage optional features).
   2. Select View features (on Windows 10, Add a feature).
   3. Search for and select OpenSSH Client, then select Add (on Windows 10, Install).
   4. When it finishes, close and reopen PowerShell.

Step 2: Connect

1. Type the command below and press Enter. It opens a secure connection to your server; it doesn’t change anything there.

   ssh username@203.0.113.10

2. If your login details give a port other than 22, use this instead, replacing PORT with the number:

   ssh -p PORT username@203.0.113.10

The first time you connect

Your computer hasn’t seen this server before. SSH shows the server’s fingerprint, a code starting with SHA256: that identifies the server, and asks Are you sure you want to continue connecting. The end of that line reads (yes/no)? or (yes/no/[fingerprint])?, depending on your SSH version.

1. If you have the server’s fingerprint (for example from a support ticket), check it matches. To check it first, type no, press Enter and ask for it in a support ticket.
2. Type yes and press Enter. A line starting Warning: Permanently added appears. That’s normal: your computer has saved the server’s identity, so you won’t be asked again.
3. When you see username@203.0.113.10's password:, type your password and press Enter. Nothing appears on screen while you type; that’s normal.

How to tell it worked

The PS C:\... prompt is replaced by the server’s prompt. It shows your username and the server’s name and ends in $ (or # when you’re root), for example username@server:~$ or [username@server ~]$. Commands you type now run on your VPS. Type exit and press Enter to disconnect.

Troubleshooting

• Connection timed out: check the IP address and port. Some office and public networks block SSH; try another network, such as your phone’s hotspot.
• Connection refused: the port is probably wrong. Check the login details we gave you.
• Permission denied: if it says Permission denied, please try again, the username or password is wrong; passwords are case-sensitive. If it ends with Permission denied (publickey), the server accepts only an SSH key for this user. After two or three failed tries, stop: repeated failures can block your IP address. Open a support ticket instead.
• A warning that says REMOTE HOST IDENTIFICATION HAS CHANGED: SSH stops and won’t connect. Don’t try to get around it. This is expected if your server’s operating system was reinstalled, but it can also mean you’re not reaching your own server. Open a support ticket and ask about your server’s key fingerprint. Only when support tells you the change is expected, remove the old entry with ssh-keygen -R 203.0.113.10 (with a port other than 22: ssh-keygen -R "[203.0.113.10]:PORT"). This deletes only your computer’s saved copy for that server. Then connect again.
• More fixes: how to troubleshoot SSH connection problems.

Still need help?

Open a support ticket from the Client Portal at my.bluearctic.com. Our support page explains how the 24/7 helpdesk works. Include your VPS IP address, the exact command you typed (without the password), the full error text, the time you tried and your own public IP address (search the web for “what is my IP”). Never include a password or a private key.