Reinstalling the operating system: which OS to choose and what to do first
A reinstall replaces a broken system or a poorly chosen distribution with a clean installation in minutes; the price is that all data on the server is erased. This guide explains what to export beforehand, how to choose among the 31 templates and what to do first after the installation.
What does a reinstall do?
Reinstall OS replaces your server's disk with the template you choose. All data on the server is erased, including files, databases, users, configuration and installed software, and the operation cannot be undone. In the form, you set a new root password (Administrator on Windows).
The installation takes a few minutes on Linux and up to 10 minutes on Windows. First-boot settings such as the network, the password and the disk are completed in the background after the server starts, so it is normal if you cannot connect the moment the installation finishes.
Snapshots sit on the same storage as the server; do not count on a snapshot as your safety net before a reinstall. Everything you want to keep must have a copy outside the server.
Before you start: move data and configuration off the server
First create a staging directory on the server and archive what you need there, then pull that directory to your own computer or to another server. The /etc archive is not meant to be unpacked wholesale onto the new system; it is there so you can look up old settings and carry over what you need.
mkdir -p /root/migration && cd /root/migration
# Databases (MariaDB; on older MySQL releases the command is mysqldump)
mariadb-dump --single-transaction --routines --triggers --events --all-databases \
| gzip > db-$(date +%F).sql.gz
# If you use PostgreSQL
runuser -u postgres -- pg_dumpall | gzip > pg-$(date +%F).sql.gz
# Configuration, site files and scheduled jobs
tar czf etc.tar.gz /etc
tar czf www.tar.gz /var/www
tar czf cron.tar.gz /var/spool/cron
crontab -l > crontab-root.txt
systemctl list-timers --all > timers.txt
cp /root/.ssh/authorized_keys authorized_keys-root.txt
# List of manually installed packages
apt-mark showmanual > packages.txt # Ubuntu / Debian
dnf repoquery --userinstalled > packages.txt # AlmaLinuxThe list is not the same for every server; depending on your application, also include user files under /home, applications under /opt, Docker volumes and compose files, and secret files such as an application's .env. The Nginx configuration (/etc/nginx), /etc/fstab with its extra disk mount lines and the Let's Encrypt certificates (/etc/letsencrypt) are already in the /etc archive. If you are moving to a different MariaDB major version, dump the application databases separately with --databases app1 app2 instead of the server-wide dump; moving the system database between versions can cause problems.
# Run on your own computer (macOS, Linux) or on a backup server
rsync -avz --progress root@203.0.113.10:/root/migration/ ./migration/
# Without rsync (including Windows PowerShell)
scp -r root@203.0.113.10:/root/migration ./
# Test that the archives are intact
gzip -t migration/*.gz && echo "archives OK"Move archives that contain secrets only to a place you trust, encrypted if possible. On a Windows server, export IIS site directories, SQL Server database backups (.bak) and application files through Remote Desktop drive sharing or your own backup tool.
Licenses: Server licenses such as cPanel, Plesk and CloudLinux are usually tied to the IP address and need to be reactivated after a reinstall. Have your license keys and account details ready before you start; for licenses bought from Hostimor, see the license pages or ask our support team.
Which operating system should you choose?
The panel offers 31 templates. For a new installation, choose a long-term support (LTS) release that is still supported. The table below summarizes common scenarios:
| Use case | Recommended template | Notes |
|---|---|---|
| General websites, Docker, PHP and Node.js applications | Ubuntu 24.04 or 26.04 LTS | Large package repository and documentation; LTS releases get 5 years of standard security updates. |
| A stable, minimal base | Debian 12 or 13 | Predictable packages that change little; a good fit for services you will not touch for a long time. |
| cPanel/WHM and RHEL-compatible software | AlmaLinux 9.5 (8.10 if required) | ABI compatible with RHEL; check which release the panel supports before you install. |
| A shared hosting server | CloudLinux 8.10 or 9.5 | Requires a CloudLinux license. |
| Previewing the next RHEL release | CentOS Stream 9 | A continuously updated development stream; prefer AlmaLinux for production. |
| .NET, IIS, MSSQL and Windows applications | Windows Server 2022 or 2025 | Installation takes up to 10 minutes; you manage it over Remote Desktop. |
| Desktop use, single-user applications | Windows 11 Pro (Windows 10 Pro if required) | Microsoft support for Windows 10 ended in October 2025. |
| ZFS, pf and BSD experience | FreeBSD 15.0 | Only if you know BSD well; the Linux commands in this Knowledge Base do not apply. |
| Authorized security testing | Kali Linux 2025.2 | Only on systems you have permission to test; the Acceptable Use Policy applies. |
The CentOS 7, CentOS 8, CentOS Stream 8, Ubuntu 18.04, Ubuntu 20.04 and Debian 10 templates are end-of-life and receive no security updates. Interim releases such as Ubuntu 24.10 and 25.04 are supported for only nine months, so their support has ended as well. Use these templates only temporarily, for compatibility with a legacy application.
Kali Linux is a rolling distribution; update the system right after installation. For FreeBSD, check the supported releases on the FreeBSD security page. If you have not yet decided between Linux and Windows, see choosing a Linux or Windows server; if you plan to install a control panel, see the control panel installation guide, since most panels require a clean installation.
Reinstall steps
- Confirm that your data is off the server and that the archives open.
- In the client area, open the Reinstall OS tool on your server's service page.
- Choose the template and set the new password. Linux requires 8 to 128 characters; Windows requires at least 8 characters and at least three of the following: uppercase letters, lowercase letters, digits and symbols.
- Read the warning and confirm.
- While the operation runs, do not close or refresh the page, and do not click the button again.
- If the panel shows that first-boot settings have not finished yet, wait a few minutes; the network, password and disk settings are being applied in the background.
Once you can connect, or from the VNC Console, you can follow the first-boot tasks from inside the server. On Windows, the same log is in C:\Windows\Temp\wisecp-task.log.
# Linux: log of the first-boot tasks triggered by the panel
tail -f /var/log/wisecp-task.logAfter the installation: the host key warning and first checks
A new installation also generates new SSH host keys for the server. Because your computer remembers the old key, the first connection shows this warning:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
...
Host key verification failed.If you reinstalled the server yourself, this warning is expected; remove the old entry and connect again. The command is the same in Windows PowerShell, macOS and Linux. If you did not reinstall, take the warning seriously and do not connect until you have verified the fingerprint from the VNC Console.
# Remove the old entry on your computer (Windows PowerShell, macOS, Linux)
ssh-keygen -R 203.0.113.10
# If you also connect by hostname
ssh-keygen -R server1.example.com
# Optionally read the new fingerprint from the server itself on the VNC Console
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pubDo not assume the IP address is the same as before; after the installation, check the IP address and username on the Sign-in Details card, and verify your DNS records and licenses against it. Then restore your data. Do not unpack the old /etc archive wholesale onto the new system, because configuration files from different releases may be incompatible. Compare and carry over only the files you need, such as Nginx site definitions, application configuration and crontabs:
# From your own computer: send the archives back to the new server
rsync -avz ./migration/ root@203.0.113.10:/root/migration/
# On the server: restore the databases (same MariaDB major version)
cd /root/migration
gunzip -c db-2026-11-21.sql.gz | mariadb
# Extract only the directory you need from the old /etc archive and compare
mkdir -p /root/old-etc
tar xzf etc.tar.gz -C /root/old-etc etc/nginx
diff -ru /root/old-etc/etc/nginx /etc/nginxFinally, secure the new system with the first 30 minutes checklist: updates, a sudo user, SSH keys, a firewall and a first snapshot. For regular backups, follow the backups with restic guide.
Frequently asked questions
Will my IP address stay the same after a reinstall?
Do not assume so. After the installation, check the IP address on the Sign-in Details card, and verify your DNS records, firewall allowances and licenses against that address.
I accidentally closed the page during the installation. What should I do?
Before you click the button again, open the page and check the server's status and the entry in the Activity Log. If the server does not come up within a reasonable time or the first-boot settings do not complete, open a support ticket with the date and time.
The console does not accept my new password.
The first-boot settings may not have finished yet; wait a few minutes. If the password contains Turkish characters or special symbols, the console's keyboard layout difference can cause trouble; the fix is in the VNC Console guide.
Related articles
- Your first 30 minutes on a new VDS or VPS: a post-setup checklist
- A server backup strategy: the 3-2-1 rule, off-site backups with restic and database dumps
- Take a snapshot before risky changes: creating and restoring restore points
- Installing a control panel on your server: cPanel, Plesk, DirectAdmin or no panel
- Automatic security updates and rebooting after a kernel update
Thanks for your feedback!