Plesk

Connect Plesk subscription and domain context to Konrado.AI with the server agent

Server integration

Plesk subscription and domain context

Use Plesk when Konrado.AI should draft replies with context from Plesk customers, subscriptions, domains, and hosting settings exposed by the integration.

Install method

Server agent

Run the generated SSH installer as root.

Platform value

plesk

Used by the installer command.

Access model

Read-only

Designed for support context, not subscription changes.

Estimated time

5 minutes

After root SSH access is ready.

What Is It?

The Plesk integration installs the Konrado.AI server agent on a Plesk host. It helps the AI understand which subscription, domain, customer, or hosting resource is relevant to a ticket.

What It Can Do

Capability	How it helps support
Subscription context	Confirm which Plesk subscription, customer, reseller relationship, plan, domain, mailbox, database, FTP user, backup, or PHP context is involved
Domain diagnostics	Resolve whether a domain is main, subdomain, or alias, then read DNS, SSL, mail, FTP, database, logs, files, and owner context
Email investigation	Check mail accounts, mailbox presence, recent Exim/Postfix delivery logs, bounces, rejections, deferrals, and queue state
System context	Read server stats, license details, service plans, traffic, resource usage, and PHP configuration
Security and backup context	Read CSF IP status, CloudLinux/LVE usage, JetBackup5 metadata, and Imunify360 malware or WAF signals when installed
Reply grounding	Combine Plesk data with WHMCS, SupportPal, and indexed documentation

Data Available To AI

Data area	What Konrado.AI can use in replies
Subscription and ownership	Plesk subscription, customer, reseller relationship, service plan, limits, expiration, associated domains, and server-wide subscription context
Domain setup	Main domain, subdomain, alias relationship, IP, hosting type, document root, DNS records, SSL certificate data, logs, and key file configuration
Email evidence	Mail accounts, mailbox storage presence, recent Exim/Postfix delivery log summaries, bounces, rejections, deferrals, and mail queue signals
Hosted resources	Databases, database users, FTP users, scheduled tasks, PHP handlers, installed PHP extensions, traffic, and resource usage
Backups	Subscription or server backup metadata when available through Plesk or JetBackup5
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, delete, upgrade, or modify subscriptions, customers, or service plans	The integration returns context for support replies; subscription actions stay in Plesk or billing
Change DNS, mailboxes, SSL, PHP, databases, files, FTP users, scheduled tasks, or limits	The tool can read these areas but does not apply customer-impacting changes
Restore backups, clean malware, unblock IPs, or clear mail queues	JetBackup, Imunify360, CSF, and mail log data are diagnostic signals only
Reveal passwords, tokens, private keys, or raw secrets	Secrets must stay out of generated replies
Prove external registrar, CDN, nameserver, or third-party mail state by itself	Plesk context must be combined with DNS checks, ticket context, or provider-specific integrations when the issue is outside the server
Perform server maintenance or arbitrary shell operations	Konrado.AI uses Plesk data for read-only investigation, followed by operator review

The Plesk integration uses the Konrado.AI server agent installed on the Plesk server. Keep installation credentials private, run the installer only from a trusted root shell, and use static IP allowlisting when the panel or server endpoint is restricted.

Ticket Examples

Example ticket questions

"The customer cannot tell which Plesk subscription owns this domain. Is it a main domain, subdomain, or alias?"
"Email is missing from a Plesk mailbox. Is there mailbox storage or delivery evidence on the server?"
"Outgoing mail is bouncing or stuck. Are there recent delivery failures or queue signals?"
"SSL does not cover an alias. Does the certificate context show why the domain is not included?"
"The site shows a 500 error. Is there PHP, log, or file context that helps explain the failure?"
"The customer is asking about restore options. Is there backup context available before escalation?"

Prerequisites

Access to Konrado.AI Integrations.
Root SSH access to the Plesk 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 Plesk.

Log in to the target server via SSH as the root user.
Copy the installation command from the Plesk 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=plesk

Run the command as root. The script installs the Konrado.AI MCP server agent on the selected server or hosting panel.

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.

Plesk installation modal showing a successful server connection

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 Plesk server
Status stays waiting	Confirm the server can reach `app.konrado.ai` over HTTPS
Subscription data is missing	Confirm the integration was created as Plesk and installed on the right server
Wrong customer context	Confirm the ticket includes enough customer, domain, or billing data to match Plesk 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.

Plesk installation modal showing a connection error

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.