Solus2
Connect SolusVM2 VPS, backup, storage, and task context to Konrado.AI
Use Solus2 when Konrado.AI needs VPS and virtualization context from a SolusVM2 environment.
What Is It?
The Solus2 integration lets Konrado.AI read SolusVM2 VPS context while drafting replies. It is useful when support tickets ask about VM status, backups, disk allocation, service specs, or recent operations.
What It Can Do
| Capability | How it helps support |
|---|---|
| Diagnose VM issues | Check VM specifications, status, IPs, plan, compute resource, and service context |
| Answer backup questions | Read available SolusVM2 backups for the VM referenced by the ticket |
| Snapshot context | Read snapshot information so agents can see whether snapshots exist before escalating |
| Storage troubleshooting | Read VM disk configuration and sizes |
| Track operations | Read VM-related task history to spot failed jobs or relevant recent changes |
| Verify VM specs | Confirm allocated resources match what the customer expects |
| Enrich replies | Combine SolusVM2 data with WHMCS, SupportPal, and knowledge-base content |
Data Available To AI
| Data area | What Konrado.AI can use in replies |
|---|---|
| VM identity and specs | SolusVM2 VM ID, status, plan, compute resource, IP addresses, and resource details |
| Backups | Available backup records for the VM referenced by the ticket |
| Snapshots | Snapshot records for the VM, useful before escalating restore or rollback questions |
| Disks | Disk configuration and size information |
| Task history | Recent VM-related task history, including signals that may explain failed provisioning, backup, or infrastructure operations |
What It Cannot Do
| Not supported | Why this matters |
|---|---|
| Power on, power off, reboot, or reset VMs | The integration is read-only |
| Create, delete, restore, download, or schedule snapshots/backups | Recovery actions must remain an operator-controlled process |
| Rebuild, reinstall, resize, migrate, or modify CPU, RAM, disk, IP, or other resources | Resource changes require manual review in your provisioning workflow |
| Run bulk operations across multiple VMs | Context is gathered for the ticket being handled |
| Replace human approval for infrastructure changes | Konrado.AI should help explain and diagnose, not mutate services |
| Match a ticket to a VM without a reliable VM ID or billing/service mapping | SolusVM2 tools require vm_id, so WHMCS, SupportPal, or ticket metadata must provide enough context |
Security Model
Create a dedicated SolusVM2 API token for Konrado.AI and treat it as a secret. The documented integration is read-only: use it to answer and diagnose tickets, not to perform power, restore, snapshot, or resource-modification actions.
Ticket Examples
- "The customer says their VPS is offline. What status, IP, and plan context is available for the linked VM?"
- "The customer is asking for a restore. Are there backups available for this VPS?"
- "Before escalating a rollback request, does this VM have any snapshots?"
- "The VPS appears to be out of storage. What disk configuration is assigned to it?"
- "The customer says the VPS resources are wrong. Do the CPU, RAM, and disk match the plan?"
- "Provisioning or a recent change failed. Is there task history that explains what happened?"
Prerequisites
- Access to Konrado.AI Integrations.
- Root SSH access to the server where the integration agent will run.
- SolusVM2 API details for the SolusVM2 instance.
- Outbound network access from the server to Konrado.AI and SolusVM2.
Installation
In Konrado.AI, open Integrations > Applications, click Add Integration, and choose Solus2.
- Log in to the target server via SSH as the root user.
- Copy the installation command from the Solus2 modal.
- Run the command in the SSH session.
- Wait for automatic connection detection in Konrado.AI.
The generated command will look like this:
bash <(curl -s https://repo.konrado.ai/init.sh) --api-key=YOUR_API_KEY --callback-url=https://app.konrado.ai/api/integrations/servers/install --platform=solus2Add SolusVM2 API Details
Solus2 also requires these SolusVM2 API values:
| Field | Description |
|---|---|
SOLUSVM2_URL | Hostname or base URL of your SolusVM2 instance |
SOLUSVM2_API_TOKEN | Dedicated SolusVM2 API token used by the integration |
Create a dedicated API token for this integration. Manage tokens in the SolusVM2 User Auth API: https://docs.solusvm.com/en/solusvm2/api-reference/api/#tag/User-Auth
Verify Success / Failure
After running the installer, Konrado.AI waits for the server to report back. A successful installation shows Connected Successfully in the installation modal and marks the integration as Connected.
If the agent connects but Solus2 data is missing, verify the SolusVM2 URL and API token before reinstalling the agent.
Troubleshooting
| Issue | What to check |
|---|---|
| Agent connects but Solus2 data is missing | Verify SOLUSVM2_URL and SOLUSVM2_API_TOKEN |
| API authorization fails | Create a new dedicated SolusVM2 API token and update the integration configuration |
| Status stays waiting | Confirm the server can reach app.konrado.ai over HTTPS |
| VM data does not match the ticket | Confirm billing or ticketing data includes enough VPS, hostname, domain, or IP context |
Installation Failure Commands
If the installation modal shows Connection Error, check both server plugin services, read the recent logs, then restart the plugin services.
systemctl status konrado-server.service konrado-root.service
journalctl -u konrado-server.service -u konrado-root.service --since "15 minutes ago" --no-pager
systemctl restart konrado-server.service konrado-root.service
systemctl enable konrado-server.service konrado-root.service
ss -ltnp | grep ':8000'After the services restart, run Test Connection again in Konrado.AI. If the status still fails, check firewall rules and make sure Konrado.AI can reach the server plugin URL.
Remove
Use Uninstall Plugin to remove the agent, then delete the integration in Konrado.AI and revoke the dedicated SolusVM2 API token if it is no longer needed.