First-Day Checklist for a New VPS
Short answerOn day one: confirm the VPS is active, save your primary IP and login details, connect (SSH on Linux / RDP on Windows), change the initial password, install updates, set a basic firewall, and decide how you will back up important data. VPSGrid plans are unmanaged.
Overview
Use this checklist after provisioning finishes. OS-specific deep dives:
- Linux: Getting Started with a Linux VPS (and SSH guides linked below)
- Windows: Getting Started with a Windows VPS
1) Confirm the VPS is ready
- Log in to the client area
- Open Services → My Services and select the new VPS
- Confirm status is active/online
- Copy the primary IP and initial credentials from the product details / VPS Ready email
2) Connect successfully once
- Linux: SSH to the primary IP (usually
root@IPon port 22) — SSH connection guide · What Is SSH? - Windows: RDP to the primary IP as Administrator — RDP connection guide · What Is RDP?
Use the browser console (noVNC) from the product page before changing firewall rules. See How to Use the Console When SSH or RDP Fails.
3) Change the initial password
- Replace the welcome password with a long, unique password and store it securely
- On Linux, consider adding SSH keys soon after first login
- On Windows, change the Administrator password from inside the desktop session
4) Install updates
- Ubuntu/Debian:
apt update && apt upgrade(reboot if the kernel requires it) - AlmaLinux/Rocky:
dnf update(reboot if required) - Windows: Settings → Windows Update → install pending updates
5) Set a firewall baseline
- Allow only what you need: SSH (
22) or RDP (3389), plus web ports (80/443) if you host sites - Do not disable the firewall to “make things work”
- Keep a console session available while testing new rules
6) Decide on backups and monitoring
- Identify critical data (sites, databases, configs) and how you will copy it off-box
- Note your service ID and primary IP for faster support tickets
- Only install software you intend to run — fewer services means less exposure
7) Optional hardening next
- Linux: SSH keys, disable password login later, fail2ban/UFW as appropriate
- Windows: RDP hardening — Secure RDP on Windows VPS
- Both: create a non-root / non-Administrator daily user when your workflow allows
Important notes
- VPSGrid manages the hypervisor, primary IP connectivity, power controls, and billing — not day-to-day guest OS admin on unmanaged plans
- Windows licensing is typically BYOL — Licensing Requirements
- Current plan specs are on the store pages; this checklist does not publish pricing
Frequently Asked Questions
Does this replace the Linux or Windows getting-started guides?
No. This is the cross-platform day-one checklist. Follow the Linux or Windows getting-started article for OS-specific detail.
Should I open every port on day one?
No. Start with remote admin access only, then open application ports when you deploy services.
What if updates break SSH or RDP?
Use the client-area console to recover, then review firewall and remote-access services before reconnecting.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net with your service ID, primary IP, OS, and which checklist step failed.
Was this answer helpful?
