Decide whether to reinstall
Use OS Re-Install only after choosing a fresh-OS recovery route and proving a separate backup and restore plan. It removes data from the reinstalled disk.
Even if the panel offers a primary-disk-only reinstall, verify the selected disk and separately preserve every required volume. A same-server snapshot is insufficient as the only recoverable copy; expect to rebuild settings, firewall rules, keys, DNS targets and licences.
Decide whether reinstall is appropriate
SSH is inaccessible but the console works
Diagnose guest network, service and firewall first.
The website application is broken
Review application logs and restore a tested application backup first.
The guest OS is compromised
Contain access and preserve needed evidence, then plan a clean build and credential rotation.
A fresh OS is explicitly required
Verify the external backup, downtime authority and restore plan before reinstalling.
A reinstall is not a general repair button. It removes the existing installation and may destroy evidence that would have explained a fault.
If compromise is suspected, retain incident evidence and rotate exposed credentials through a clean route; reinstalling alone does not establish that other systems are safe.
Prepare a recoverable path
- Identify the correct VPS and confirm who owns the data and approves downtime.
- Make a current backup outside the VPS; verify that it is readable and includes databases, files, configuration and any required secrets through a secure process.
- Record the current OS, IP addresses, application dependencies and recovery steps. Arrange a maintenance window and tell affected users.
- Check that the target OS image and required licences are available for this service. If any item is uncertain, stop and ask support before clicking Reinstall.
If this VPS runs MariaDB or PostgreSQL, follow the VPS database backup preflight to check exports, off-VM custody and an isolated restore before reinstalling.
Illustrative go/no-go: if the only backup is on the disk being reinstalled, stop. Obtain a separately held copy and demonstrate that the needed database and files can be read or restored.
Reinstall and verify
In the VPS management panel, choose OS Re-Install, select the intended distribution and version, and set a strong new root password as prompted. Read the confirmation carefully, including any primary-disk-only option. After the task completes, use the console to confirm boot, then update packages, configure access and restore data from the verified backup. Test the application, mail, TLS and monitoring before announcing service recovery.
If anything fails
Do not repeat the reinstall to treat an unexplained boot or network failure. Record the panel task state, timestamp and console output, then contact Novasean support. Customer-managed VPS users own guest data and restore planning; Novasean can investigate platform-side task failure. A managed arrangement may allocate more recovery work, but only its agreed service schedule defines that scope.
Restore and check dependencies
After the new image boots, confirm the expected IP addresses and DNS, apply security updates, restore accounts and applications through the approved backup route, and rotate credentials that were exposed or copied. Test from outside the VPS: web pages, database transactions, scheduled tasks, outbound mail and monitoring. If the service used external DNS or a licence bound to an OS installation, verify those separately. Keep the original backup until the owner has accepted the new service state.
Will secondary disks survive? Virtualizor documents a primary-disk-only option, but do not treat a UI option as a substitute for a backup or assume it is enabled for your VPS. Can support recover data after reinstall? Recovery depends on an existing usable backup; do not assume deleted guest data can be reconstructed.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.