SSH is the standard way to administer a Linux VPS. This walkthrough covers Windows Terminal / PowerShell, macOS/Linux Terminal, and PuTTY, plus the failures we see most often in support.
Gather connection details
From your VPS provider panel, note:
- Public IPv4 (and IPv6 if you use it)
- Username (
root,ubuntu,debian, or a custom sudo user) - Auth method: password (temporary) or SSH key
- SSH port if not
22
macOS and Linux (OpenSSH)
ssh USER@YOUR_IP
# custom port:
ssh -p 2222 USER@YOUR_IP
# specific key:
ssh -i ~/.ssh/id_ed25519 USER@YOUR_IP
First connect asks you to trust the host key fingerprint—compare it with the fingerprint shown in the provider panel when available.
Windows: OpenSSH in Terminal
Modern Windows includes OpenSSH Client:
ssh USER@YOUR_IP
Generate a key (ed25519 preferred):
ssh-keygen -t ed25519 -C "your@email"
type $env:USERPROFILE\.ssh\id_ed25519.pub
Paste the public key into ~/.ssh/authorized_keys on the server (one line, mode 600 on the file and 700 on .ssh).
Windows: PuTTY
- Install PuTTY.
- Host Name:
USER@YOUR_IPor IP with username prompted. - Port:
22unless changed. - For keys, convert with PuTTYgen or use Pageant.
- Save a session so you are not retyping IPs.
Copy files
scp ./file.tar.gz USER@YOUR_IP:~/
sftp USER@YOUR_IP
Common errors
| Symptom | Likely cause | Fix |
|---|---|---|
| Timed out | Firewall / wrong IP | Provider console; allow 22/tcp |
| Permission denied (publickey) | Key not installed or wrong user | Fix authorized_keys, check key path |
| Permission denied (password) | Bad password or root login disabled | Reset via panel; use sudo user |
| Host key verification failed | IP reused, key changed | Confirm rebuild; then update known_hosts |
Next step
Once you can log in reliably, harden the service: keys only, no password root login, and optional allow lists. Continue with How to Harden SSH on a VPS.
Related guides
- How to Harden SSH on a VPS
- How to Open Ports on a Linux VPS (UFW, firewalld, iptables)
- VPS Port Forwarding Explained (Firewall vs Home Router)
- How to Point Your Domain to Chapter22 Hosting
Frequently Asked Questions
Should I log in as root?
Only long enough to create a sudo user and install your SSH key. Daily work should use an unprivileged account.
Connection timed out—password never asked. What failed?
Usually network path: wrong IP, provider firewall blocking 22/tcp, or the VM firewall dropped SSH. Use the provider console to repair rules.
Can I SSH to a Windows VPS?
Yes if OpenSSH Server is installed and allowed through Windows Firewall. Many Windows operators still use RDP for desktop admin; SSH is excellent for scripting.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.
