Skip to main content

​
Starting Fresh with a Server Rebuild

The Rebuild feature lets you completely wipe your virtual server and reinstall the operating system from scratch. Think of it as formatting your entire computer and reinstalling Windows or Linux — everything on the drive is erased and you start with a blank slate. This is a powerful tool when you genuinely need it. But it is also the most destructive action available in the control panel, which is why the Rebuild button is the only one colored red.

Difficulty

Intermediate

Time

5-10 Minutes
A rebuild permanently deletes EVERYTHING on your server. Every file, every database, every configuration, every piece of installed software, every user account — all of it is gone the moment the rebuild begins. This action is completely irreversible. There is no undo button. There is no “are you sure you’re really sure?” second chance after confirmation. Once it starts, your previous server environment is gone forever.Always create a backup before rebuilding. If you have anything on the server you want to keep — even a single configuration file — back it up first.

​
What Exactly Happens During a Rebuild?

To understand the severity, here is exactly what a rebuild does:
  1. Your current operating system is destroyed — the virtual disk is wiped clean.
  2. A fresh OS image is written — the new operating system is installed from a clean template.
  3. A new root password is generated — your old credentials no longer exist.
  4. Your selected SSH keys are injected — if you chose any during the rebuild.
  5. The server boots into the new OS — as if it were a brand-new server.
Everything from before the rebuild — your websites, applications, databases, configuration files, cron jobs, firewall rules, SSL certificates, uploaded files, custom software, user accounts — is permanently erased. The only thing that survives is your server’s IP address, which remains the same.

​
Before You Rebuild

This checklist is not optional. Run through every item before you click that red button.
1

Create a Backup

This is the most important step. If you have any data you care about, back it up now.
  • Use the Backups tab in the control panel to create a full server backup.
  • Or manually download important files via SFTP or SSH.
  • Export your databases using mysqldump, pg_dump, or your database’s export tool.
  • Save copies of configuration files (/etc/nginx/, /etc/apache2/, .env files, etc.).
Do not assume you can recover anything after a rebuild. You cannot.
2

Document Your Configuration

Make a note of everything you will need to recreate your server environment:
  • Installed software and versions
  • Custom firewall rules and iptables configurations
  • SSH keys and authorized users
  • Cron jobs (crontab -l to list them)
  • DNS records that point to this server
  • Any services or daemons you configured
3

Disable Server Protection

If you have Rebuild Protection enabled (and you should on any server you care about), you must disable it before the Rebuild button becomes clickable. Click the lock icon below the server name on the Overview page to remove protection. See How to Protect Your Server from Accidental Rebuilds for details.
4

Notify Anyone Who Uses This Server

If other team members, clients, or users have access to this server, let them know. Everything they have on the server will be destroyed. Give them time to save their own data and prepare for the downtime.

​
Performing the Rebuild

1

Navigate to Your Server

Click on Servers in the top navigation bar, then click Manage next to the server you want to rebuild.
2

Click the Rebuild Button

On the server’s Overview page, locate the row of power control buttons at the top. The Rebuild button is on the far right, colored red to distinguish it from the blue power controls (Boot, Shutdown, Restart, Power Off). Click it.If the Rebuild button appears greyed out or disabled, you have Server Protection enabled. Disable it first by clicking the lock icon below the server name.
3

Select an Operating System

Choose the operating system you want to install. Available options typically include:
  • Debian (various versions)
  • Ubuntu (LTS and current releases)
  • AlmaLinux / Rocky Linux (RHEL-based)
  • CentOS
  • Windows Server (depending on your plan)
You can choose the same OS you had before (for a clean reset) or switch to a completely different one.
4

Choose SSH Keys (Optional)

If you have SSH keys stored in your account, select which keys to inject into the new installation. This allows you to log in via SSH immediately after the rebuild without needing a password — a best practice for security.
5

Confirm the Rebuild

Review your selection carefully. You will be asked to confirm that you understand all data will be permanently erased. This is your last chance to back out. If you are certain, confirm to begin the rebuild process.
6

Wait for Completion

The rebuild typically takes between 1 and 5 minutes. You can monitor progress in the Task Log at the bottom of the server page. Once complete, the task will show 100% COMPLETE and your server will be running the new operating system.

​
After the Rebuild

Once the rebuild is finished, you are working with a completely fresh server:
  • Your server is running the newly installed operating system.
  • A new root password has been generated — check your email or the panel for the credentials.
  • Any SSH keys you selected during the rebuild are installed and ready.
  • Your server’s IP address is unchanged — no DNS updates needed.
  • Connect via SSH (Linux) or RDP (Windows) to begin setting up your new server environment.
  • Re-enable Rebuild Protection immediately. Click the lock icon below the server name to safeguard your freshly configured server.
After rebuilding, your very first action should be to re-enable Rebuild Protection. You just went through the trouble of setting up a new server — protect it from being accidentally wiped again.

​
When to Use Rebuild

Rebuilding is a big step. Here are the scenarios where it makes sense:

Switch Operating System

You want to move from one Linux distribution to another (say, Ubuntu to Debian), or switch between Linux and Windows. A rebuild is the only way to change the OS on your VPS.

Clean Slate

Your server has accumulated layers of old software, conflicting configurations, and leftover files from experiments. Sometimes it is faster to start fresh than to untangle the mess.

Recovery from Severe Misconfiguration

You have broken something fundamental — the SSH daemon will not start, the file system is corrupted, or the bootloader is damaged. When a server is so broken that Rescue Mode cannot save it, a rebuild gets you back to a working state.

Security Incident

If your server has been compromised by an attacker, a complete rebuild is the safest response. It ensures that all malicious software, backdoors, rootkits, and unauthorized modifications are completely removed. Change all passwords and SSH keys afterward.

​
What NOT to Use Rebuild For

A rebuild is not the answer to every problem. Before you reach for the red button, consider these alternatives:
ProblemBetter Solution
A service crashed and will not restartRestart the server first, or troubleshoot via SSH / Rescue Mode
You want to update the operating systemUse apt upgrade or dnf update via SSH — no rebuild needed
Your disk is fullClean up old files, logs, and caches via SSH
You forgot your root passwordUse the Password Reset feature in the control panel
One application is misbehavingReinstall just that application, not the entire OS
No. A rebuild is permanent and irreversible. Once the process begins, all previous data is erased and cannot be recovered by any means. The only way to get your data back is from a backup created before the rebuild. This is why we emphasize backing up so strongly.
No, your server’s IP address remains the same after a rebuild. You do not need to update DNS records, firewall rules, or any external configurations that reference your server’s IP.
You have Server Protection enabled — which is a good thing. It means your server is safeguarded against accidental rebuilds. To proceed, click the lock icon below the server name on the Overview page to temporarily disable protection. See How to Protect Your Server from Accidental Rebuilds for the full guide.
A typical rebuild completes in 1 to 5 minutes. You can track real-time progress in the Task Log section at the bottom of the server management page. If it seems stuck, give it up to 10 minutes before contacting support.
Yes. Rebuilding with the same OS gives you a completely fresh installation — as if the server were brand new. This is useful when you want a clean slate without switching distributions.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!
Last Updated: March 2026 | VPS Support: Server rebuilds simplified.