The first day with a new VPS is the best time to get the fundamentals right — before any real traffic or data depends on the server. This checklist covers exactly what to do, in order.
1. Connect and Verify Access
Confirm you can connect via SSH (or RDP for Windows Server) using the credentials from your provisioning email. See How to Connect to Your VPS via SSH (Windows, macOS & Linux).
2. Update the System
sudo apt update && sudo apt upgrade -ySee How to Update and Upgrade Your Ubuntu or Debian VPS for the full process.
3. Create a Non-Root Sudo User
Avoid working as root day-to-day. See How to Create a New User with Sudo Access on a Linux VPS.
4. Set Up SSH Key Authentication
Move away from password-based login as soon as possible — see the key setup steps in SSH Hardening: Change the Port, Disable Root Login & Use SSH Keys.
5. Enable a Firewall
See How to Configure UFW Firewall on a Linux VPS — deny by default, allow only what you need.
6. Set the Correct Timezone
sudo timedatectl set-timezone UTC
sudo timedatectl set-ntp trueSee How to Set the Correct Timezone and Enable NTP on a Linux VPS for why this matters.
7. Note Your Server Details
Record your IP address, chosen hostname, and OS version somewhere accessible — all of this is also visible anytime in your VPS For Life Client Area.
8. Install Fail2Ban
See How to Install and Configure Fail2Ban on Ubuntu & Debian to automatically block brute-force login attempts.
9. Plan Your Backup Strategy
Decide how you'll back up this server before you actually need to restore something — see How to Set Up Automated VPS Backups.
10. Bookmark Your Support Options
Know where to go if something goes wrong: the VPS For Life support ticket system and your Client Area's service management page.
The Condensed Version (For the Impatient)
If you want all of this as copy-paste commands in one pass, see How to Harden a Fresh Linux VPS in 15 Minutes.
What NOT to Do in the First 24 Hours
- Don't deploy production data before completing basic hardening
- Don't skip the firewall step "just to test something quickly" — it's easy to forget to come back to it
- Don't ignore the provisioning email — it often contains details (initial password, specific IPs) you'll need later
FAQ
Do I really need to do all of this before deploying my application?
At minimum, steps 1-5 (access, updates, sudo user, SSH keys, firewall) should happen before any production data touches the server — they take under 20 minutes total and prevent the most common early-life security issues.
Continue Reading
- How to Harden a Fresh Linux VPS in 15 Minutes
- VPS Security Checklist for Beginners
- How to Order and Deploy Your First VPS with VPS For Life
Browse more articles in Getting Started / VPS Basics.
