Manage a VPS
Control power, access, reinstall, snapshots, backups, and firewall settings.
Manage the full VPS lifecycle from one place
After a VPS is provisioned, you can check status, control power state, recover access, change SSH keys, manage snapshots and backups, reinstall the server, and apply firewall policies.
First troubleshooting step
Check whether the VPS is still provisioning before treating it as an outage. A service that is not finished provisioning needs a different response than a running service with a network problem.
VPS lifecycle, network access, and backups
After a VPS is provisioned, you can track its state, change power state, recover access, update SSH keys, and manage snapshots or backups from the portal.
What customers can do today
- Check VPS runtime status, power state, uptime, CPU, memory, and network counters.
- Start, stop, and reboot a VPS.
- Reset the root password and receive the new password once.
- Reinstall with a supported operating system selection and optionally specify hostname, SSH key, or firewall policy.
- Update the VPS SSH key after provisioning.
- List, create, roll back, and delete snapshots.
- View backup state, configure backup schedules, run backups, cancel running backup jobs, delete backup files, and restore from backup.
- Review and apply the effective firewall policy for the service.
What to check first after provisioning
- Confirm the service status is active.
- Confirm the expected IP assignment is present in the service details.
- Confirm the access path you plan to use first: SSH key, password, or console workflow.
- Confirm whether backup coverage is already enabled for that workload.
How to think about recovery features
Snapshots and backups solve different problems. Snapshots are useful around short-lived change windows. Backups are the recovery mechanism you should plan around for service loss, rollback, or scheduled protection.
Practical operating advice
- Record the service ID, host or IP details, and owner.
- Set the SSH key and firewall policy before the VPS becomes a shared production dependency.
- Use snapshot actions before risky maintenance.
- Treat backup schedule review as part of service acceptance, not as an afterthought.