Proxmox
Connect Proxmox VM, container, node, and resource context to Konrado.AI
Use Proxmox when Konrado.AI should help answer VPS, VM, container, node, or resource questions with context from your Proxmox environment.
What Is It?
The Proxmox integration installs the Konrado.AI server agent where it can read virtualization context. It helps support agents understand VM/container status, allocated resources, IP context, node placement, and recent operational signals when available.
What It Can Do
| Capability | How it helps support |
|---|---|
| Diagnose VM or container issues | Check QEMU VM or LXC status, config, node, VM ID, runtime signals, and selected Proxmox data groups |
| Verify plan/spec questions | Compare expected CPU, RAM, disk, and network configuration with the VM/container config returned by Proxmox |
| Storage troubleshooting | Read disk definitions and backup availability when exposed by the Proxmox CLI data |
| Recent operations context | Read snapshots, backups, replication, firewall, and metrics data when requested |
| Ticket-specific investigation | Keep the query scoped to the VM/container referenced by the ticket instead of scanning the whole cluster |
Data Available To AI
| Data area | What Konrado.AI can use in replies |
|---|---|
| VM identity | Node name, VM or container ID, virtualization type, and whether the requested guest exists |
| Status and configuration | Current runtime status, Proxmox configuration, allocated CPU, RAM, disk, network, and device definitions when available |
| Metrics | CPU, memory, disk I/O, and network history from Proxmox metrics when available |
| Storage and recovery context | Disk definitions, snapshot records, and backup records for the referenced VM or container |
| Network and operations | Firewall rules or options, replication data, and operational signals that may explain a ticket-specific issue |
What It Cannot Do
| Not supported | Why this matters |
|---|---|
| Power on, power off, reboot, or reset VMs | The integration is documented as read-only |
| Create, delete, or restore snapshots/backups | Destructive or state-changing operations stay outside Konrado.AI |
| Modify CPU, RAM, disk, network, or storage allocation | Resource changes require operator review in Proxmox |
| Migrate VMs, change HA settings, or alter node/cluster configuration | Infrastructure maintenance remains an operator-controlled workflow |
| Guarantee live monitoring or alerting coverage | The integration answers ticket-time questions from the data it can read |
| Perform bulk operations across VMs or nodes | The integration is for ticket-specific context |
Security Model
The Proxmox integration is intended for read-only troubleshooting context. Install the agent from a trusted root SSH session, protect the generated API key, and restrict network access to Konrado.AI static IPs when your Proxmox environment is firewalled.
Ticket Examples
- "The customer's VPS appears offline. What status and configuration are visible for the referenced VM or container?"
- "The customer says their VPS plan includes more CPU, RAM, or disk. Does the current allocation match the service?"
- "The VPS is slow during peak hours. Do CPU, memory, disk I/O, or network metrics show pressure?"
- "The customer wants a restore. Are there snapshots or backups for this VM before we escalate the request?"
- "The service is unreachable from outside. Is there firewall or replication context that may explain it?"
- "The ticket only mentions a VM ID. Which node and virtualization type should support use for the investigation?"
Prerequisites
- Access to Konrado.AI Integrations.
- Root SSH access to the target Proxmox server.
- Outbound HTTPS access from the server to Konrado.AI.
- If inbound access is restricted, allow the Konrado.AI static IP addresses.
Installation
In Konrado.AI, open Integrations > Applications, click Add Integration, and choose Proxmox.
- Log in to the target server via SSH as the root user.
- Copy the installation command from the Proxmox 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=proxmoxVerify 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 connection fails, use the troubleshooting commands below and run Test Connection again.
Troubleshooting
| Issue | What to check |
|---|---|
| Command fails immediately | Confirm you are running it as root on the target Proxmox server |
| Status stays waiting | Confirm the server can reach app.konrado.ai over HTTPS |
| VM data is missing | Confirm the integration was created as Proxmox and installed in the right environment |
| Ticket does not match a VM | Confirm billing or ticket data includes enough service, 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 from the server, then delete the integration in Konrado.AI.