VPS hosting for beginners: sizing, SSH, firewall and backups
A VPS (virtual private server) is a slice of a physical server with its own operating system and root access. Unlike shared hosting, you control everything — which is exactly why the first hour matters so much.
What a VPS is (and is not)
You get dedicated CPU, RAM and disk guarantees, not a shared pool.
You get root, so software and configuration are entirely up to you.
You are responsible for security, updates and backups.
It is not 'managed' unless the plan says managed.
Sizing: start small
For a single website, a small site, a VPN or a small app, 1 vCPU and 1–2 GB RAM is usually plenty. Add more RAM before more CPU — most web workloads run out of memory first. You can resize later.
1. Log in and set up SSH keys
Do not rely on a password for root. Generate a key pair locally, add the public key to the server, then disable password authentication.
ssh-keygen -t ed25519 -C "you@laptop"
ssh-copy-id [email protected]
# then in /etc/ssh/sshd_config:
PasswordAuthentication no
PermitRootLogin prohibit-password2. Turn on a firewall
Allow only what you serve — typically 22 (SSH), 80 and 443 (web) — and drop everything else.
ufw allow 22
ufw allow 80
ufw allow 443
ufw enable3. Apply updates automatically
Unpatched servers are the most common way machines get compromised. Enable unattended security updates.
apt update && apt upgrade -y
apt install unattended-upgrades -y
dpkg-reconfigure --priority=low unattended-upgrades4. Set up backups you have tested
A backup you have never restored is not a backup. Schedule snapshots plus off-server copies of your data, and practise a restore once so you know the steps.
Common beginner mistakes
Leaving password SSH enabled for root.
Opening every port 'just in case'.
Never testing the restore path.
Ignoring disk space until the server fills up.
Get these four right and your VPS will be safer and easier to live with than most. Our VPS plans come with full root and a console, so you can practise on a small box today.