How to Initialize a Cloud VPS Restoring It to Original Conditions
Introduction
In SeFlow you can initialize a Cloud VPS to restore it to its original state — the same condition it was in when first deployed. This procedure fully resets the system by reinstalling the selected template and removing all files, configurations, and data added afterwards.
Initialization is useful when:
- you want to start again from a clean system;
- you need to quickly reinstall the operating system;
- a misconfiguration prevents the VPS from working properly;
- you need to prepare the VPS for a new use or a new customer.
Tip: Always perform a backup before initializing the Cloud VPS. The process is irreversible and all data on the server will be permanently deleted.
What Initializing a Cloud VPS Means
Initializing a Cloud VPS includes:
- complete deletion of all data on the VPS disks;
- full system formatting;
- reinstallation of the original template or OS selected at creation;
- restoring the service to its factory state.
Tip: The public IP address and network settings remain unchanged after initialization, so DNS and external configurations do not need to be updated.
Prerequisites
- Access to the SeFlow Control Panel.
- A VPS that is operational and not in an error state.
- Awareness that all data will be deleted.
How to Initialize the Cloud VPS
Follow these steps to restore the Cloud VPS to its original condition:
- Log in to the SeFlow Control Panel.
- Navigate to the Cloud VPS section.
- Select the VPS you want to initialize.
- Open the Initialization tab (or equivalent).
- Review the information shown and confirm that you understand the data loss involved.
- If requested, select the template or OS to reinstall.
- Click INITIALIZE VPS.
- Wait for the process to complete.
The VPS will switch to an Initializing state and will be unavailable until the reinstallation is finished.
Tip: Initialization time typically ranges from 2 to 10 minutes depending on the selected OS.
What Happens After Initialization
Once initialization is completed:
- the VPS will be accessible again using the default credentials provided at creation;
- the selected template (Linux, Windows, Plesk, etc.) will be applied;
- network settings (IP, gateway, DNS) will remain unchanged;
- snapshots, installed packages, custom configurations, and saved files will no longer be present.
Tip: After initialization, immediately update the operating system (apt, yum, Windows Update) and reconfigure required services (web server, database, firewall, control panels, etc.).
When Not to Initialize
Avoid initializing the VPS if:
- you need to recover files, logs, or databases (data deletion is irreversible);
- you want to test a change without losing the current setup (use snapshots instead);
- the issue could be resolved with a simple reboot or small software adjustment.
Tip: Use snapshots as an alternative when you may want to revert quickly without a full reset.
Best Practices
- Take a full backup before initializing.
- Write down credentials and configuration details before wiping the system.
- Notify clients or team members involved in the project.
- After initialization, immediately update the operating system and reinstall essential software.
- Verify that key services (web, database, applications) are working correctly.
Tip: In production environments, always schedule initialization during a maintenance window to prevent unexpected service disruption.
