cPanel
Connect cPanel hosting context to Konrado.AI with the server agent
Use cPanel when Konrado.AI should answer hosting-account questions with context from a cPanel server.
What Is It?
The cPanel integration installs the Konrado.AI server agent on a cPanel host. The agent gives Konrado.AI hosting context it can use while drafting replies, especially when a ticket mentions a domain, hosting account, package, quota, or service state.
What It Can Do
| Capability | How it helps support |
|---|---|
| Account lookup | Identify the cPanel username, owner, plan, domains, quota, disk, databases, email accounts, FTP accounts, SSL, backups, and PHP context |
| Domain diagnostics | Check domain ownership, addon/parked/subdomain relationships, DNS records, SSL data, logs, file tree, usage, and key config files |
| Email investigation | Check mail accounts, forwarders, autoresponders, mailbox presence, recent Exim delivery logs, bounces, rejections, deferrals, and queue state |
| System context | Read cPanel/WHM version, load, bandwidth, packages, services, reseller data, user disk usage, user bandwidth, and backup availability |
| Security and backup context | Read CSF IP status, CloudLinux/LVE usage, JetBackup5 metadata, and Imunify360 malware or WAF signals when those tools exist on the server |
| Ticket enrichment | Combine cPanel context with WHMCS, SupportPal, and Knowledge Base content |
Data Available To AI
| Data area | What Konrado.AI can use in replies |
|---|---|
| Account and ownership | cPanel username, owner/reseller relationship, plan, quota, associated domains, and account status context |
| Domain setup | Main, addon, parked, and subdomain relationships, document root, IP address, DNS zone records, SSL certificate data, and PHP context |
| Email evidence | Email accounts, forwarders, autoresponders, mailbox storage presence, recent delivery log summaries, bounces, rejections, deferrals, and mail queue signals |
| Usage and performance | Disk usage, bandwidth, account statistics, load, service status, and CloudLinux/LVE resource history when available |
| Backups | JetBackup5 account, backup, download, job, schedule, destination, queue, log, and alert metadata when JetBackup is installed |
| Security | CSF IP status and Imunify360 or ImunifyAV malware, scan, WAF, infected-domain, blocked-port, and proactive-defense context when available |
What It Cannot Do
| Not supported | Why this matters |
|---|---|
| Create, suspend, terminate, upgrade, or modify hosting accounts | The integration returns context for support replies; account actions stay in WHM/cPanel or your billing workflow |
| Change DNS, email routing, mailboxes, PHP versions, SSL certificates, files, databases, or cron jobs | The tool can read many of these areas, but it does not apply customer-impacting changes |
| Restore backups, clean malware, unblock IPs, or clear mail queues | JetBackup, Imunify360, CSF, and Exim data are diagnostic signals only |
| Reset passwords or expose secrets | Passwords, API tokens, private keys, and mailbox contents are not meant to be placed in AI replies |
| Prove external DNS, registrar, CDN, or third-party mailbox state by itself | cPanel data must be combined with DNS checks, ticket context, or provider-specific integrations when the issue is outside the server |
| Run arbitrary shell operations | The documented support flow is read-only investigation, followed by operator review |
Security Model
The cPanel integration uses the Konrado.AI server agent installed on the target host. Treat the generated API key as a secret, run the installer only on servers you manage, and restrict inbound access with IP allowlisting when your environment is firewalled.
Ticket Examples
- "example.com stopped working after a DNS change. Is the domain attached to the right cPanel account and document root?"
- "Webmail looks empty for sales@example.com. Is there mailbox storage on the server?"
- "Messages from example.com are bouncing or delayed. Is there delivery-log evidence we can mention in the reply?"
- "AutoSSL is failing for an addon domain. Does the domain ownership or certificate context explain the issue?"
- "The hosting account is out of disk space. Is the usage mostly files, mail, databases, backups, or logs?"
- "The customer says this domain is theirs, but billing does not match. Is it on a reseller child account?"
Prerequisites
- Access to Konrado.AI Integrations.
- Root SSH access to the cPanel server.
- Outbound HTTPS access from the server to Konrado.AI.
- If inbound panel/API access is restricted, allow the Konrado.AI static IP addresses.
Installation
In Konrado.AI, open Integrations > Applications, click Add Integration, and choose cPanel.

- Log in to the target server via SSH as the root user.
- Copy the installation command from the cPanel 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=cpanelVerify 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 cPanel server |
| Status stays waiting | Confirm the server can reach app.konrado.ai over HTTPS |
| Panel data is missing | Confirm this server actually runs cPanel and the integration was created as cPanel |
| Wrong customer context | Confirm the ticketing integration can map the customer or domain to the cPanel data |
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.