# SolusVM 2 https://docs.wisecp.com/fr/solusvm2 Connect SolusVM 2 to provision virtual servers and handle their daily management from WISECP. ## Accessing the Screen Open **Products → Hosting & Servers → Server Settings → Add New Server**. Select **SolusVM 2** under **Server Automation Module → Virtualization**. Address: `{admin}/products/servers/add`. ## Before Connecting In the SolusVM administrator panel, open **Access → API Tokens → Generate API Token**, enter a name, and select **Generate**. The [official token instructions](https://docs.solusvm.com/en/solusvm2/billing-integration-guide/prepaid-billing/installation-and-configuration/initial-configuration/) explain that you cannot view the token again after closing it. Store it securely. Prepare the management node, an available location, compute resource, plan, IP pool, and operating system image. The token needs access to users, plans, servers, and the tool operations you intend to use. WISECP needs an available module license, an active server, and a priced server product. Saved servers include **Preferences**, **Linked Services**, and **Import**. ## Connection and Product Settings - **Address / Hostname**: Required. Enter the management node address without a scheme or API path. There is no separate port field; SSL selects HTTPS or HTTP. - **Username / Password / API Token**: The shared form requires a username and password. API authentication uses the required API Token; a user password does not replace it. - **Verify SSL Certificate**: Enabled for new records. Keep SSL and verification enabled with a valid certificate. - **Identity and Capacity**: Monthly Cost defaults to zero; select its currency. Empty Maximum Accounts becomes 200. Occupancy alerts follow this limit; Nameservers accepts four entries. - **Plan / Default Location**: Creation requires a valid plan. An unselected location uses the first available location. The plan list reads up to 500 records. - **Default Operating System / Application**: Initially unselected. A selected application replaces the operating system and User Data. The order's operating system selection overrides the default. - **User Data (cloud-init)**: Optional and initially empty. Sends startup configuration to a new server when no application is selected. - **Automatic Backups**: Disabled by default. Enabling it requests a daily 00:00 schedule; the provider's backup infrastructure must be ready. - **Default User Role / Default Limit Group**: Optional. Applied to new provider accounts; they do not change an existing account matched by email. - **Additional Disk Offer**: Selectable, but current creation and management operations do not apply it. Do not promise disk delivery through this setting. ## Tasks ### Connecting the Server 1. Complete **Connection Details** and click **Test Connection**. The test reads the token's account. 2. Complete **Identity and Capacity** and click **Add New Server**. Later edits use **Save Changes**. 3. Verify the saved record. A successful connection test does not verify creation, deletion, or every tool permission. ### Preparing the Product 1. In the server product's **Automation → Module Assignment** section, select **SolusVM 2**. 2. Choose **Single Server** or **Server Group** under **Server Configuration**. Complete **Module Configuration**. 3. Keep the initial product hidden and **Automatic Setup** disabled. Set prices and currency. 4. Click **Save Changes** and verify the server and plan mapping. Order requirements support **Operating System**, **Hostname**, **Root Password**, and optional **SSH Public Key** mappings. Map operating system values to provider image version IDs. Requirements and saleable addons are not created automatically. Available addons cover extra vCPU, RAM (MB), disk (GB), traffic (GB), IPv4, IPv6, and automatic backups. Resource addons resize the plan. IPs remain assigned during suspension and are released when the addon is cancelled. Verify IP or backup option upgrades separately; their scope differs from resource upgrades. ### Mapping Existing Servers In a saved server, open **Import → List Results** to see hostnames, IPs, and VM IDs. Select clients, products, periods, and dates, then use **Import** below. Files and passwords are not transferred. The current import does not transfer VM ID into the required service mapping. Correct and verify **VM ID** under **Management → Settings → Integration Settings** before enabling automation. Saving **Plan** or **Automatic Backup** here does not itself submit a provider resize operation. ### Managing the Service Correctly mapped services offer creation, suspension, reactivation, termination, password changes, and plan upgrades. New provider accounts are matched using the client's email. Administrators and clients inspect server status and resources under **Management → Overview**. Management tools include start, stop, restart, OS reinstall, hostname, VNC, and rescue mode. They also cover snapshot and backup creation/restoration/deletion, reverse DNS editing, and IPv4/IPv6 allocation/removal. Start is hidden for running servers; stop and restart are hidden for stopped servers. Activity logs and total traffic are displayed; traffic history is unavailable. Backup downloads, SSH terminal, firewall, ISO, and separate disk management are not provided. The panel shortcut signs into the client account once; administrator panel SSO is unavailable. Periodic usage collection reads CPU, disk, traffic, IP counts, and backup/snapshot counts. Live RAM usage is unavailable. Missing data can appear as zero. CPU, disk, and traffic metric maximums can change provider resources. Prices and plan catalogs are not synchronized periodically. Before enabling automation, compare VM ID, owner, plan, tools, and usage against the provider on an existing test service. Evaluate destructive operations only on a disposable test service with a verified backup. ## Important Notes > **Data and Resource Changes** > > Termination deletes the server; reinstalling and restoring overwrite current data. Rescue mode restarts the server. IPs, backups, and resource changes can affect provider costs; verify backups and capacity first. ## Required Permissions Server settings require **MODULES_SERVERS_SETTINGS**; product editing requires **PRODUCTS_OPERATION**. Service tools follow administrator permissions and client access restrictions. ## Related Articles - [Adding a Server](https://docs.wisecp.com/en/adding-a-server) - [Product Automation](https://docs.wisecp.com/en/product-automation) - [Service Management](https://docs.wisecp.com/en/service-management)