How to Connect to Your Server With SSH (Windows, Mac & Linux)

SSH (Secure Shell) is how you get a command line on your VPS or dedicated server. It sounds intimidating but it is really one command. Here is how to connect from Windows, macOS and Linux, with keys and the common errors covered.

The basic SSH command

On macOS and Linux, SSH is built in — just open Terminal. On Windows 10/11 it is built into PowerShell and Command Prompt (or use PuTTY). The command is the same everywhere:

ssh username@your-server-ip

# example
ssh root@203.0.113.10

The first time you connect you will be asked to confirm the server's fingerprint — type yes. Then enter your password (the cursor will not move as you type — that is normal) and you are in.

Connecting on a custom port

If your host (or your own hardening) moved SSH off the default port 22, add -p and the port number:

ssh -p 2222 username@your-server-ip

Connecting with an SSH key

Key-based login is more secure than a password — see how to harden SSH. Point to your private key with -i:

ssh -i ~/.ssh/id_ed25519 username@your-server-ip

On Windows with PuTTY you load the .ppk private key under Connection → SSH → Auth instead.

Using PuTTY on Windows (the classic way)

1. Download and open PuTTY.
2. Enter your server IP in Host Name and the port (22 by default).
3. Click Open, accept the fingerprint, then log in with your username and password.

Common SSH errors

• Connection refused / timed out — wrong service, firewall or IP. See connection refused.
• Permission denied (publickey) — a key or auth problem. See permission denied (publickey).
• Too many authentication failures — too many keys offered. See this fix.

Once you are in, a few essential Linux commands will get you productive fast.

Staying connected: avoiding drop-offs

An SSH session that keeps freezing or disconnecting when idle is usually a network or keepalive issue, not a login problem. Adding a ServerAliveInterval to your client config (or the equivalent keepalive in PuTTY) sends a small packet periodically so routers and firewalls don't silently drop the idle connection.

What to do right after your first login

On a fresh server, your first jobs are security ones: switch to key-based login, then lock things down. Follow how to harden SSH, put up a firewall with UFW, and work through the full VPS hardening checklist before you host anything public.

Tips for a smoother SSH experience

• Save hosts in a ~/.ssh/config file so you can type "ssh myserver" instead of the full command.
• Use SSH keys rather than passwords — more secure and no typing the password each time.
• Keep your host's VNC/console details handy in case SSH ever locks you out.
• Never share your private key; only the public key ever goes on the server.