SolusVM 2 VPS provisioning
Sell SolusVM 2 plans as FluxBilling products: API token, plugin install, products, order form, customer controls, billing lifecycle and troubleshooting.
The SolusVM2 plugin connects FluxBilling to the API of your SolusVM 2 panel, so you can sell SolusVM 2 plans as FluxBilling products. FluxBilling takes the order, sends the invoice and collects the payment. When the invoice is paid, the plugin creates the server in SolusVM 2, and the customer manages it from the FluxBilling client area. The plugin is free and is listed in the plugin marketplace of every FluxBilling panel. Your SolusVM 2 installation and licence stay as they are.
This guide covers plugin version 1.8.0, which needs FluxBilling 0.0.1572 or newer. It walks through the setup in the order you do it, then explains what happens to a server over its life and what to check when something does not work. The plugin talks to the SolusVM 2 API only; it does not connect to SolusVM 1.
Who supports this integration. The plugin is built and maintained by FluxBilling. If something does not work, contact FluxBilling support at contact@fluxbilling.app or through fluxbilling.app/contact. Questions about SolusVM 2 itself, its licence or its servers go to SolusVM support.
What you need before you start
- A working SolusVM 2 installation whose management node FluxBilling can reach over HTTPS.
- At least one plan in SolusVM 2. The plan sets the CPU, RAM, disk and limits of the server.
- At least one location with compute resources that can build that plan. In FluxBilling, each SolusVM 2 location is a location your customers can choose.
- IP addresses for those compute resources in SolusVM 2. SolusVM 2 assigns the addresses when it creates the server.
- The OS images you want to sell, set up in SolusVM 2.
- Network access from your FluxBilling panel to the SolusVM 2 panel. For the VNC console, FluxBilling also needs to reach the VNC address and port that SolusVM 2 reports for each server (see VNC console).
Step 1: Create an API token in SolusVM 2
The plugin sends every request with a SolusVM 2 API token. We recommend a separate token for FluxBilling, so you can replace it without touching anything else.
- Log in to the SolusVM 2 administrator interface as an administrator. The token acts for the user who creates it, and the plugin needs to create users and servers for your customers.
- Go to Access → API Tokens and click Generate API Token.
- Enter a name, for example FluxBilling, and generate the token.
- Copy the token straight away and keep it somewhere safe. SolusVM 2 does not show it again once you close the dialog; if you lose it, generate a new one.
SolusVM documents these steps in its initial configuration guide. The full SolusVM 2 API reference lists every request below.
| Request | Used for |
|---|---|
GET /plans, GET /locations, GET /os_images, GET /plans/{id} | The plan, location and operating system lists (every page is read), the connection test, and the plan's traffic allowance and port speed |
GET /users, POST /users, GET /users/{id}/projects | Finding or creating the customer's SolusVM 2 user and its default project |
POST /servers, GET /servers/{id}, DELETE /servers/{id} | Creating the server, reading its details and usage, terminating it |
POST /servers/{id}/start, /stop, /restart, /suspend, /resume, /reinstall, /reset_password, /vnc_up, /resize | Power, suspend and unsuspend, reinstall, root password reset, VNC console and plan changes |
/servers/{id}/backups, /backups/{id}/restore, /servers/{id}/snapshots, /snapshots/{id}, /snapshots/{id}/revert | Backups and snapshots |
GET /tasks, POST /users/{id}/tokens, POST /reverse_dns, PATCH /reverse_dns/{id} | Recent activity, the one-time login link for Control Panel, reverse DNS |
Step 2: Install the plugin
- In the FluxBilling admin panel, open Settings (the gear icon in the top bar).
- Under Integrations, open Marketplace. Stay on the Browse tab.
- Open the SolusVM2 card and click Get for Free.
FluxBilling confirms with Plugin "SolusVM2" installed and ready to use. The plugin is switched on straight away and appears under Settings → Integrations → Plugins as SolusVM2 Provider, marked Active.

Step 3: Connect it to SolusVM 2
- Open Settings → Integrations → Plugins.
- On the SolusVM2 Provider card, click Configure.
- Fill in the two fields below and click Save Configuration.
| Field | What to enter |
|---|---|
| SolusVM2 Panel URL (required) | The base address of your SolusVM 2 panel, with nothing after the host name, for example https://solus.example.com. Do not add the API path: FluxBilling adds it itself. A self-signed certificate is accepted. |
| API Token (required) | The token from step 1. The hint under the field names the SolusVM 2 menu Account → API Tokens; in current SolusVM 2 versions it is Access → API Tokens. |
The token is stored encrypted. FluxBilling shows Configuration saved successfully when the settings are saved.
Test the connection. In Settings → Integrations → Plugins, click SolusVM2 Provider, open the Connections tab and click Test connection on the SolusVM2 API row. The plugin reads one plan with your token, so a wrong token fails: you see Connected to SolusVM 2: the API token was accepted. or, for example, Test failed: SolusVM rejected the API token (HTTP 401).
Step 4: Create a category for your SolusVM 2 products
In FluxBilling, the category decides how its products are delivered. Every product in the category is built by the plugin you choose here.
- Open Products, switch to the Categories tab and click Add Category.
- When FluxBilling asks What does this category sell?, choose Plugins. Do not choose VPS: that type is FluxBilling's own KVM module, not SolusVM 2.
- Enter a Name. The URL slug fills in by itself.
- Under How paid orders are fulfilled, click SolusVM2 Provider.
- Under Availability, choose Live to show the category on the order page, or Unlisted while you test.
- Click Create Category.
Step 5: Create a product for each SolusVM 2 plan
- On the Products tab, click Add Product and choose the category from step 4.
- On General, enter the product name and description your customers will see.
- On Configuration, fill in the SolusVM 2 fields described below.
- On Pricing, set the price. Prices, billing cycles, taxes and add-ons all live in FluxBilling. Only the plan, locations and operating systems come from SolusVM 2.
- Click Create Product.
| Field | What it does |
|---|---|
| Plan (required) | The SolusVM 2 plan this product builds. CPU, RAM, disk and limits come from the plan. |
| Available Locations (required) | The SolusVM 2 locations customers can order in. The order form offers only these. |
| Available OS Images (required) | The operating systems customers can choose at checkout. Each version of an OS image in SolusVM 2 is one entry, for example Ubuntu 24.04. |
| Allow OS Selection, Allow Location Selection | On: the customer chooses at checkout. Off: the order form does not ask, and the order takes the first operating system or available location on the product's list. |
| Auto-generate Password | On: FluxBilling generates the root password and the order form does not ask for one. |
| Hostname Template | Optional. When set, FluxBilling generates the hostname and the customer is not asked for one. {{id}} is replaced by the service number, so vps-{{id}}.example.com becomes for example vps-1042.example.com. Leave it empty to let customers enter a hostname. |
The Pricing tab also lists your locations under Location Pricing, so you can charge extra for a location, and shows the add-on the plugin understands (see the next step).
Step 6 (optional): Sell additional IPv4 addresses
Each server gets the addresses its SolusVM 2 plan provides. To let customers order extra IPv4 addresses, create one add-on and attach it to your SolusVM 2 products.
- Open Products, switch to the Options tab and click Add Option.
- Enter an Option Name such as Additional IPv4 addresses.
- Under Slug, choose additional_ips — SolusVM2 Provider. This is the name the plugin reads. A different slug is not seen by the plugin.
- Leave Spec Service on None (billing only).
- Choose a Pricing Type, then switch on Configurable Options.
- Add one choice per address count. The Value is the number of extra IPv4 addresses, on top of the main one. So
1means one extra address and2means two. Give each choice its label and price. - Leave IPAM Allocation on each choice set to Not set. SolusVM 2 assigns these addresses itself.
- Click Create.
- Open each SolusVM 2 product, go to Pricing and use Attach under Plugin expects these options, or select the add-on in the list. It then shows as attached.
- An add-on without configurable choices counts its quantity, so a single add-on adds one extra address.
- SolusVM 2 adds extra addresses only when the plan allows additional IPs. Check this on the plan in SolusVM 2 before you sell the add-on.
The add-on takes effect when the server is built. The plugin does not add or remove addresses on an existing server, so customers cannot change, add or cancel the add-on after the build: the service page shows the current choice and asks them to open a ticket. You can still change it from the admin panel. FluxBilling then bills the new choice and adds a pending task under Automations as a reminder; add or remove the addresses for that server in SolusVM 2 yourself.
Step 7: Place a test order
Place an order for each product before you sell it, for example from a test client account. Depending on the product's settings, the order page asks for the location, the operating system, a hostname and a root password, plus any add-ons you attached.
Hostnames may contain letters, numbers, hyphens and dots, and each part between the dots must start and end with a letter or number. Otherwise the form shows Hostname must be a valid hostname (e.g. server1.example.com) — no spaces, @, or special characters. Ask customers for a strong root password: the same password is also given to the SolusVM 2 user the plugin creates for a new customer.
What happens when the invoice is paid
With Auto Provisioning switched on (see Billing lifecycle), FluxBilling starts the build as soon as the invoice is paid:
- The SolusVM 2 user. The plugin looks for the SolusVM 2 user whose email address matches the customer's exactly (case is ignored), reading the user list page by page if SolusVM 2's search does not answer usefully. If there is none, it creates an active user with that email address and the root password of this order as its password.
- The server. It asks SolusVM 2 to create the server in that user's default project, with the plan, the chosen location and operating system, the hostname (also set as the server's FQDN), the root password and the number of extra IPv4 addresses from step 6. Scheduled SolusVM 2 backups are switched off for the new server.
- Hand-over. FluxBilling saves the SolusVM 2 server ID and the main IPv4 address on the service and marks it Active. With the default email templates, the customer gets an email that the server is ready, with its IP address and root password.
Every hour FluxBilling also reads the IP address, hostname and location of each server back from SolusVM 2 and updates the service, so changes you make in SolusVM 2 show up in FluxBilling.
What your customers can do
In the client area, the customer opens the service. The server actions sit in the page header (the first ones as buttons, the rest under More). The page itself has the sections Overview, Plan & network, Access, Backups, Snapshots and Recent activity, all filled from SolusVM 2. A figure SolusVM 2 does not report shows as a dash, not as zero.

| Card | What it shows |
|---|---|
| Server | Status, Hostname, OS, Location, IPv4, Connect (the SSH command, for example ssh root@203.0.113.10, or the RDP address for Windows) and Created. |
| Usage | Tiles refreshed every 30 seconds: CPU in percent, RAM allocated (SolusVM 2 reports no memory use), Disk used of the disk size, Traffic used of the plan's allowance. |
| Plan | Plan, vCPU, RAM, Disk, Traffic (the allowance, or Unmetered), Port speed (or No limit) and the number of IPv4 addresses. |
| Network | Gateway, Netmask, Resolvers, Reverse DNS, Extra IPv4, IPv6, IPv6 gateway, MAC; empty rows are left out. |
| Access | Username and a masked Password. See Access card. |
| Backups | Created, Type (Manual or Scheduled), Size, Status; a Create Backup button and Restore in each row's menu. |
| Snapshots | Name, Created, Size, Status; a Create Snapshot button (with an optional name) and Revert and Delete in each row's menu. |
| Recent activity | The last five SolusVM 2 tasks for the server: Time, Action, Status. |
| Action | What it does |
|---|---|
| Start, Stop, Restart | Power actions in SolusVM 2. Start shows while the server is stopped, Stop and Restart while it is running and ask for confirmation. |
| Console | Opens the console in a FluxBilling window. See VNC console. |
| Control Panel | Opens SolusVM 2 in a new tab on a one-time login link for the customer's own SolusVM 2 user. It is refused for a server owned by an administrator account or by another user. |
| Reverse DNS | Sets the PTR record of an IPv4 address of the server: IPv4 address (empty means the main address) and Hostname. |
| Reinstall | Erases the server and installs the chosen operating system. The dialog says to use Reset Password afterwards for a new root password. |
| Reset Password | SolusVM 2 generates a new root password. FluxBilling shows it once and stores it for the Access card. If SolusVM 2 does not return it, the message says it was emailed to the server owner. |
Restore, Revert and Delete ask for confirmation and accept only backups and snapshots of this server. A restore or revert overwrites the disk; everything written since is lost. A backup runs while the server stays online. If SolusVM 2 refuses an action, its own message is shown. While a service is suspended, the actions and cards are hidden and the customer sees a Service Suspended notice with the reason.
Reinstall offers every OS image version in SolusVM 2, not only the ones you selected on the product. If you keep images in SolusVM 2 that customers should not install, remove or hide them in SolusVM 2, or take this into account.

Access card
The eye button (Show) fetches the stored root password, Copy copies it: the order's password, or the newer one from a reset. Customers can show it only while the service is active and their account is not suspended; a team member also needs the Manage Services permission. Every reveal is recorded in the activity log, without the password.
VNC console
When the customer clicks Console, FluxBilling asks SolusVM 2 to open a VNC session for the server and shows the console in FluxBilling's own console window, so the customer does not need a SolusVM 2 login. FluxBilling connects to the VNC address and port that SolusVM 2 returns. For this to work:
- VNC must be enabled for the server in SolusVM 2, and the server must be running. Otherwise the customer sees SolusVM returned no VNC port for this server — the VNC console must be enabled for it and the server must be running.
- Your FluxBilling panel must be able to reach that VNC address and port. If a firewall only allows the VNC ports from certain addresses, add your FluxBilling panel's address.

What your staff see
In the admin panel, the service page shows Root credentials with Show root password (each reveal is recorded against the staff member's account; staff need permission to edit services). Provider Controls shows the live status, Username, Virtualization, Suspended, Plan and Cluster (the SolusVM 2 compute resource), and under Server Controls the customer's actions plus Create Backup and Create Snapshot. Control Panel signs staff in as the customer's SolusVM 2 user.
Below follow Usage, Plan, Network, Backups, Snapshots and Recent activity, with the row actions as buttons. The staff Plan card adds the server's UUID and the Panel user. The order configuration (Ordered OS, Location, IPv4 add-on) is under Service Details.

Billing lifecycle
The invoice drives the server. The rules are set under Settings → Billing → Automation:
- Auto Provisioning: builds the server when the first invoice is paid. When it is off, the paid service waits as Pending until staff provision it.
- Auto Suspension with Suspension Grace: an invoice still unpaid that many days after its due date suspends the server in SolusVM 2.
- Paying the overdue invoice resumes the server in SolusVM 2 automatically, once no earlier renewal invoice for that service is still unpaid. A suspension for abuse is not lifted by a payment.
- Auto Termination with Termination Grace: a server still suspended for non-payment that many days later is terminated.
Terminating a service deletes the server in SolusVM 2. This happens when auto termination runs, when a customer's cancellation takes effect, or when staff terminate the service. It cannot be undone. Check the Termination Grace before you go live. The customer's SolusVM 2 user is kept.
Plan changes
Customers can only move between products you link on the product's Upgrade Paths tab. When an upgrade or downgrade between two SolusVM 2 products is paid, the plugin asks SolusVM 2 to resize the server to the plan of the new product. If the new product has no plan set, or SolusVM 2 refuses, the upgrade is marked as failed and the service keeps its current product. Try a plan change on a test server before you offer upgrades to customers, especially a downgrade to a smaller disk.
Updating the plugin
Open Settings → Integrations → Marketplace, switch to Installed and click Check for Updates. When a new version is available, click Update to v…. Your connection settings and products are kept.
Troubleshooting
When a build fails, the service stays Pending. The error appears in the Automations menu in the top bar of the admin panel, as Provision via Solusvm2 Provider with the reason in red and a retry button.
FluxBilling tries a failed build again by itself, up to two more times over the next minutes. After that, open the service and click Retry Provisioning, choose the operating system and, if you want, set a new root password. A build started this way does not email the customer, so use Resend Welcome on the service page once it has worked.
| Message or symptom | What to check |
|---|---|
| Test failed: SolusVM rejected the API token (HTTP 401) | The token is wrong or was deleted in SolusVM 2. Generate a new one (step 1) and save it in the plugin settings. |
| The Plan list in the product editor stays empty | FluxBilling cannot read from SolusVM 2. Run Test connection and check the panel URL (the base address only), the token and any firewall in between. If the editor says Plugin not configured, a required setting is missing. |
| Could not create the SolusVM user: … | SolusVM 2 refused to create the customer's user; its reason follows the colon. Fix the cause in SolusVM 2, then retry. |
| Failed to create server, or SolusVM 2's own message | SolusVM 2 could not be reached during the build, or refused the order, for example with a validation error about the plan, location or operating system. Fix the cause, then retry. |
| Failed to suspend server, Failed to resume server, Failed to terminate server | SolusVM 2 did not confirm the action. Check that the server still exists in SolusVM 2 and that FluxBilling can reach the panel, then run the action again from the service page. |
| Failed to start server, Failed to stop server, Failed to restart server, Failed to reinstall server, Failed to reset password, Failed to fetch OS images | The same for the server actions and the reinstall list. When SolusVM 2 sends an error, its own message is shown instead. |
| This server is not owned by your own SolusVM account, so no login link can be created | The server belongs to an administrator account or was moved to another SolusVM 2 user. Move it back to the customer's user. |
| That IP address does not belong to this server, Enter a hostname such as server1.example.com | The Reverse DNS dialog got an address of another server, or a hostname that is not a full domain name. |
| The target product has no SolusVM2 plan configured | The product the customer upgrades to has no Plan set on its Configuration tab. |
| SolusVM returned no VNC port for this server — the VNC console must be enabled for it and the server must be running | Enable VNC for the server in SolusVM 2 and start the server. See VNC console. |
| SolusVM returned HTTP … or Could not read the VNC details for this server from SolusVM | SolusVM 2 refused the request or could not be reached. Check the connection and the server in SolusVM 2. |
Limits
- Backups and snapshots use SolusVM 2's own features. New servers are created with scheduled SolusVM 2 backups switched off.
- Reverse DNS covers the server's IPv4 addresses only. Recent activity shows the last five tasks.
- The IPv4 add-on is applied only when the server is built. Customers cannot change it afterwards; when you change it in the admin panel, the price changes and you add or remove the addresses in SolusVM 2 yourself.
- IP addresses come from SolusVM 2. FluxBilling's own IP address management is not involved.
- Each FluxBilling panel connects to one SolusVM 2 installation.
- FluxBilling does not rely on callbacks from SolusVM 2: each action is judged on SolusVM 2's direct answer. You do not need to set up anything for callbacks.
Moving away from SolusVM 2 later
If you later decide to run your hypervisors with FluxBilling's own VPS module, VPS Panel Migration can take over SolusVM 2 nodes while the virtual servers keep running. It is a separate product from this free plugin.
SolusVM is a trademark of its respective owner. FluxBilling is not affiliated with SolusVM or its owner.
