This is an infrastructure-administrator procedure, not a task to run inside an ordinary customer VPS. Confirm the current management-node requirements, licence and supported OS from the vendor documentation. Prepare a dedicated clean host, a resolvable management hostname, adequate storage and memory, a restricted administration path and off-server recovery planning. The management-node requirements differ from those of compute resources, and not every virtualization environment is supported.

1. Plan the topology first: management node, compute resources, storage, address pools, network isolation and backup destinations. Decide which systems must communicate and permit only the documented ports between the appropriate endpoints.
2. Connect to the clean management server using authorized SSH access. Confirm OS support, hostname resolution, time synchronization and package/network health before installing.
3. Download and review the current vendor installer:
   Command example

   curl -fSL https://installer.dev.solusvm.com/latest -o installer
   chmod +x ./installer
   ./installer

   Obtain the address from the current vendor guide and verify the download source before execution.
4. Follow the interactive installation, provide the intended administrator email and resolvable management hostname, and accept the licence agreement only after reviewing it. Save generated credentials and the one-time login link securely.
5. Open the management interface and verify its TLS identity. Configure a trusted certificate for the hostname, change or securely store the initial administrator credential, and enable two-factor authentication.
6. Activate the appropriate licence and complete the separate compute-resource, storage, IP-block and plan setup. Configure tested notification delivery and a backup plan for the management node before customer provisioning.

Confirm the administrator interface is reachable through the intended restricted route, the certificate matches and system tasks execute. Add a controlled test compute resource and disposable test VM only after their prerequisites are met. Test management-node backup and recovery separately from guest backups.

If installation fails, examine the installer logs under the documented SolusVM log directory and preserve the exact error. Check supported OS, name resolution, outbound repository access and required inter-node connections. Avoid replaying a legacy SolusVM 1 installer or disabling all network protection to work around a failed prerequisite.

• Adding a compute resource to SolusVM 2
• Logging in to your SolusVM VPS control panel
• Managing SolusVM login alerts and account security
• Installing a VPS operating system from ISO in SolusVM 2

• SolusVM: Installation And Logging In
• SolusVM: Administration