Your first 30 minutes on a new VDS or VPS: a post-setup checklist
The first half hour after your server is delivered prevents most of the problems you would otherwise run into later. This checklist walks you through every step, from the first connection to your first clean snapshot, in order, with commands and checks.
The Sign-in Details card and your first SSH login
Once your payment is confirmed, the server is set up automatically; most orders are delivered within a few minutes. In the client area, open your server's service page and find the Sign-in Details card. It shows the username (root on Linux, Administrator on Windows), the password, hidden by default, with Show / Hide and Copy buttons, the IP address, any additional IPs and, for Linux servers, a ready-made SSH command.
Windows 10/11, macOS and Linux ship with the OpenSSH client; run the command in PowerShell or Terminal and replace 203.0.113.10 in the examples with your own IP address.
ssh root@203.0.113.10On the first connection, your client says it does not recognize the server's host key and shows a fingerprint that starts with SHA256. When you type yes, the key is saved to the known_hosts file on your computer and compared on every later connection. If you want to be thorough, open the VNC Console in the panel before accepting and display the server's own fingerprint; the two values must match.
# On the VNC Console: shows the server's own key fingerprint
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pubFor Windows servers, the card also shows a Remote Desktop (RDP) line in the IP:3389 format and a Download the RDP connection file link; the file opens in full screen, adapts to your window size and asks for your credentials. For Windows, see connecting with RDP, RDP security and Windows Server maintenance; the rest of this article covers the Linux steps.
Update the operating system
Templates are built on a specific date, so it is normal for a freshly delivered system to have pending security updates. Before you install anything else, refresh the package lists and apply all updates.
# Ubuntu / Debian
apt update && apt full-upgrade -y
# AlmaLinux 9
dnf upgrade --refresh -yIf Ubuntu or Debian asks about a modified configuration file (for example sshd_config) during the upgrade, accept the default option that keeps the locally installed version unless you are sure. If the kernel or core libraries were updated, check whether a reboot is required:
# Ubuntu / Debian: a reboot is required if the file exists
cat /var/run/reboot-required 2>/dev/null
# AlmaLinux 9 (requires the dnf-plugins-core package)
dnf needs-restarting -r
# If required
systemctl rebootAn end-of-life release (such as CentOS 7/8, Ubuntu 20.04 or Debian 10) no longer receives security fixes. If your application allows it, move to a supported LTS release with a reinstall while the server is still empty. For future updates, see the automatic security updates guide.
Secure access
A sudo user
Doing day-to-day work as a separate sudo user instead of root limits the damage of a mistyped command and makes it easier to tell who did what in the logs. Replace deploy in the example with your own username.
# Ubuntu / Debian
adduser deploy
usermod -aG sudo deploy
# AlmaLinux 9
useradd -m -G wheel deploy
passwd deploy
# Check
id deploySSH keys and turning off password login
Generate an ed25519 key pair on your own computer and copy the public key to the server. Never copy the private key (id_ed25519) anywhere; only the public key with the .pub extension goes to the server.
# On your own computer (macOS, Linux)
ssh-keygen -t ed25519 -C "laptop-2026"
ssh-copy-id deploy@203.0.113.10
# Test in a new terminal: no password prompt should appear
ssh deploy@203.0.113.10
sudo -vWindows does not include ssh-copy-id; you can do the same thing in PowerShell:
# Windows 10/11 PowerShell: instead of ssh-copy-id
ssh-keygen -t ed25519 -C "laptop-2026"
Get-Content $env:USERPROFILE\.ssh\id_ed25519.pub | ssh deploy@203.0.113.10 "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys"You can also add the public key with the panel's SSH Keys tool. It works on Linux only, accepts up to 20 keys and expects a single-line OpenSSH public key that starts with ssh-ed25519 or ssh-rsa. The panel writes the key through VMware Tools; after adding it, confirm in a new terminal that you can connect without a password.
Once key-based login works, turn off password login. In short: create /etc/ssh/sshd_config.d/00-hardening.conf, test the syntax and reload the service. The 00 prefix matters: OpenSSH uses the first value it reads for a setting, and files such as 50-cloud-init.conf in some templates can keep password login enabled.
cat > /etc/ssh/sshd_config.d/00-hardening.conf <<'EOF'
PasswordAuthentication no
KbdInteractiveAuthentication no
PermitRootLogin prohibit-password
EOF
# Syntax test and effective values
sshd -t && sshd -T | grep -Ei 'passwordauthentication|permitrootlogin'
# Ubuntu / Debian
systemctl reload ssh
# AlmaLinux 9
systemctl reload sshdKeep your current session open and try to log in from a new terminal. Details and common errors are in the SSH key login guide. Turning off SSH password login does not break the panel tools, because the panel reaches the server through VMware Tools, not over SSH.
Change the root password from the panel
The delivery password may have left traces in email or browser history; change it on day one. Do this with the panel's Reset Root Password tool rather than the passwd command inside the server. For this action the panel signs in to the server with the stored password. If you change the password inside the server, the panel can no longer sign in and the next reset attempt fails with an error saying it could not sign in to the server with the stored password.
On Linux the password can be 8 to 128 characters long. On Windows it needs at least 8 characters and at least three of the following: uppercase letters, lowercase letters, digits and symbols. Generate a long, random password and keep it in a password manager. Setting your sudo user's password inside the server with passwd deploy causes no problems; the stored password the panel uses belongs to the root account (Administrator on Windows).
Never share your password, card details or one-time codes in a support ticket, live chat or email. Our support team does not ask for them.
Hostname, time zone and time synchronization
Set the server name (hostname) with the panel's Change Hostname tool. Only lowercase letters, digits, hyphens and dots are allowed. Choose a fully qualified domain name (FQDN) such as server1.example.com and add an A record for it in your domain's DNS zone that points to your server's IP; control panels and mail software expect this match. On Windows, the same tool changes the computer name and the server restarts. See IP addresses, hostname and DNS settings for details.
The time zone determines how you read logs, cron jobs and application timestamps. To switch to Türkiye time and check the result:
timedatectl set-timezone Europe/Istanbul
timedatectl
hostnamectlThe timedatectl output should show System clock synchronized: yes and NTP service: active. If synchronization is off, turn it on with timedatectl set-ntp true. Ubuntu 24.04 and Debian usually use systemd-timesyncd, while AlmaLinux uses chrony; timedatectl timesync-status and chronyc tracking show the details, respectively. If you manage several servers, running all of them on UTC is also a valid choice; what matters is consistency. The same setting on a Windows server:
Set-TimeZone -Id 'Turkey Standard Time'
w32tm /query /statusFirewall and listening services
First check which services on the server are listening for outside connections, then set up a firewall that allows only what you need. Order matters: if you enable the firewall before allowing SSH, you cut off your own connection.
# Listening TCP/UDP ports and their processes
ss -tulpn
# Ubuntu / Debian (UFW; on Debian first run: apt install ufw)
ufw allow OpenSSH
ufw enable
ufw status verbose
# AlmaLinux 9 (firewalld)
systemctl enable --now firewalld
firewall-cmd --permanent --add-service=ssh
firewall-cmd --reload
firewall-cmd --list-allFor choosing ports, IP-specific rules and traps such as Docker bypassing your rules, see the UFW and firewalld guide. To slow down password-guessing attacks on SSH, you can then install Fail2ban. If you lock yourself out, fix the rule from the VNC Console, which works independently of the network.
Leave VMware Tools alone
All servers run on VMware ESXi. The panel's graceful shutdown, password reset, hostname, network and DNS settings, additional IP, SSH key and disk expansion actions all run through VMware Tools inside the server (open-vm-tools on Linux). Changes you save while the server is off or Tools is not running are applied once the server is on and Tools is running. The power actions guide explains how power operations depend on Tools.
Do not remove the open-vm-tools package, stop its service or mask it. When cleaning up packages (apt autoremove, dnf remove), do not confirm the operation if open-vm-tools appears in the list of packages to be removed.
# Ubuntu / Debian
systemctl status open-vm-tools --no-pager
# AlmaLinux 9
systemctl status vmtoolsd --no-pager
# Version (any Linux distribution)
vmware-toolbox-cmd -v
# In-server log of panel actions
tail -n 50 /var/log/wisecp-task.logOn Windows the service is called VMTools; check its status in PowerShell with Get-Service VMTools. On Windows, the log of panel actions is in C:\Windows\Temp\wisecp-task.log.
Your first clean snapshot and a backup plan
When the system is up to date, access is secured and the basic settings are done, take your first snapshot with the panel's Snapshots tool. Give it a name that says when and why it was taken, for example clean-install-2026-11-21. You can keep at most 2 snapshots at a time, and snapshots must be deleted before a disk expansion or a server migration. Keeping a snapshot for a long time slows down the disk; think of it as a restore point for the next few days. See the snapshot guide for details.
A snapshot is not a backup: it lives on the same storage as the server and disappears with it if the server is deleted. Unless your package explicitly includes backups, backing up your data is your responsibility. Use the backup strategy with restic guide to set up automatic, encrypted off-server backups, and read the Backup and Data Retention Policy for the scope.
Summary: the 30-minute checklist
Times are approximate.
| Step | Command or panel tool | Time |
|---|---|---|
| 1. Get the connection details and connect | Sign-in Details, ssh root@IP | 2 min |
| 2. Update the system | apt full-upgrade / dnf upgrade | 5–10 min |
| 3. Create a sudo user | adduser + usermod -aG sudo / useradd -G wheel | 2 min |
| 4. Add an SSH key, turn off password login | SSH Keys, ssh-copy-id, 00-hardening.conf | 5 min |
| 5. Change the root password | Reset Root Password | 1 min |
| 6. Set the hostname and time | Change Hostname, timedatectl | 3 min |
| 7. Set up the firewall | ufw / firewall-cmd | 5 min |
| 8. Check VMware Tools | systemctl status open-vm-tools | 1 min |
| 9. Take the first snapshot | Snapshots | 2 min |
| 10. Plan backups | Off-server backups with restic | plan separately |
Once the server starts taking load, follow the resource monitoring guide, and if resources run short, the resource upgrade guide.
Frequently asked questions
I changed the root password with passwd and the panel reset now fails. What should I do?
Log in over SSH or the VNC Console, change the root password back to the one shown on the Sign-in Details card, then make the change from the panel. If you do not know the old password, open a support ticket, and do not include your password in the message.
After a while I get a REMOTE HOST IDENTIFICATION HAS CHANGED warning. Why?
If you reinstalled the operating system, the server's host key has changed and the warning is expected; remove the old entry with ssh-keygen -R 203.0.113.10 and connect again. If you did not reinstall, do not connect, and verify the fingerprint from the VNC Console.
Should I add swap space?
First check with swapon --show whether the template already has swap. A small swap file prevents out-of-memory (OOM) kills during sudden spikes but is no substitute for RAM; see the swap guide for details.
Related articles
- Sign in with an SSH key and turn off password login
- Setting up a Linux firewall with UFW and firewalld
- Take a snapshot before risky changes: creating and restoring restore points
- A server backup strategy: the 3-2-1 rule, off-site backups with restic and database dumps
- IP addresses, additional IPv4, hostname and DNS resolver settings
Thanks for your feedback!