- Docs
- Guides
Hosting-ops AI agent for cPanel & DirectAdmin
The hosting-ops agent lets your AI assistant — and your teammates, with one click — check and fix a customer’s cPanel or DirectAdmin hosting right from the chat: a website that’s down, email that doesn’t arrive, an expired SSL certificate or an IP the server blocked. It is included with Pro, Lifetime and Reseller accounts.
Beta. The checks follow cPanel’s and DirectAdmin’s official API documentation and were tested against servers that answer exactly as documented. Real servers can differ (versions, plugins, token privileges); if a check says something that doesn’t match your server, tell us and we’ll fix it.
What it can do
| Action | What it looks at or does | Runs |
|---|---|---|
| Website check | Answers the site gives over HTTPS/HTTP, whether the domain’s DNS points to the server, whether the account is suspended (and why), disk and file (inode) use, the PHP version and the latest error-log lines. | On its own |
| Email check | MX, SPF, DKIM and DMARC records, mailboxes that are (nearly) full, outgoing mail suspended or held, and delivery failures from the last 24 hours. | On its own |
| SSL check | The live certificate of the domain and its www — trusted or not, issuer, expiry — and what the panel has installed, including AutoSSL problems on cPanel. | On its own |
| Issue or renew SSL | Runs AutoSSL for the account (cPanel) or requests a Let’s Encrypt certificate for the domain and its www (DirectAdmin). Refused while the domain’s DNS points elsewhere. | On its own (a safe fix) |
| Blocked IP check | Whether an IP is blocked by cPHulk on cPanel, or on DirectAdmin’s login blacklist. Without an IP it checks the address the customer is chatting from. | On its own |
| Unblock IP | Removes an IP that cPHulk blocked automatically after failed logins. Never a block an admin made by hand. | On its own (a safe fix) |
Change who may run each action — the AI on its own, the AI after a teammate approves, teammates, admins — in Settings → AI → AI actions. With test mode on, the two fixes are only described (a dry run).
Whose account it touches
- The customer must be verified first (signed in, an email code or the WHMCS support PIN).
- The account must host the domain the customer names and belong to the verified email: their own service in WHMCS, or a cPanel / DirectAdmin account whose contact email is theirs. For anyone else’s domain the answer is simply “not found” — it never says whose it is.
- An IP is only unblocked when it is a public address, and only the one IP — never a whole list. If you store visitor IPs shortened for privacy (Settings → Security), the IP the customer chats from is not used.
- Every check and fix is on the conversation’s timeline and in Settings → AI → AI actions → Activity.
Two ways to connect your servers
Use either or both. When both are set up, WHMCS is asked first; a domain that isn’t one of the client’s services there is looked up on the servers you added.
Through your WHMCS module (nothing to enter in TalkingDot)
- Update the TalkingDot WHMCS module to 1.2: Settings → Integrations → WHMCS → Download, upload it over the old one.
- In WHMCS, Addons → Addon Modules → TalkingDot → Configure: Hosting checks and Hosting fixes are on by default.
The module finds the client’s own active cPanel or DirectAdmin service for the domain and uses the server login WHMCS already has (its API token or password). The login never leaves WHMCS.
Add a cPanel / WHM server
- In WHM: Development → Manage API Tokens → Generate Token.
- Privileges: a token of
rootwith all privileges gives every check. A reseller’s token works for that reseller’s accounts, but the blocked-IP check and unblock need root. Limit the token to the IP address our requests come from if you can. - In TalkingDot: Settings → AI → AI actions → Hosting servers → Add server, choose cPanel / WHM, enter the host name, user (
rootor the reseller) and the token. It’s tested when you save.
Add a DirectAdmin server
- In DirectAdmin (as admin, or a reseller): Login Keys → Create key. Leave Allow HTM off.
- Allow at least:
CMD_API_LOGIN_TEST,CMD_API_DOMAIN_OWNERS,CMD_API_SHOW_USER_CONFIG,CMD_API_SHOW_USER_USAGE,CMD_API_POP,CMD_API_ADDITIONAL_DOMAINS,CMD_API_SSL,CMD_SSLandCMD_SHOW_LOG— andCMD_API_ADMIN_FILE_EDITORfor the blocked-IP check. DenyCMD_LOGIN_KEYS,CMD_API_LOGIN_KEYSandCMD_PASSWD. - Add the IP address our requests come from to DirectAdmin’s
ip_whitelist: DirectAdmin blacklists an address after failed logins, and a mistyped key would otherwise lock us out. - In TalkingDot: Settings → AI → AI actions → Hosting servers → Add server, choose DirectAdmin and enter the host name, user and key.
Keys are stored encrypted, are never shown again and never reach the AI. Server addresses must be public.
What it doesn’t do (yet)
- CSF firewall. CSF (on cPanel and DirectAdmin) has no API that can remove only automatic blocks, so it isn’t checked or changed. The AI says so and hands the chat to your team.
- Unblocking on DirectAdmin. DirectAdmin has no safe API to remove an IP from its blacklist or the Brute Force Monitor; the AI reports the block and a teammate removes it.
- Delivery failures on DirectAdmin appear only on versions with DirectAdmin’s email-log API.
- The latest error lines on cPanel come from the site’s
error_logon cPanel 138 and newer, otherwise from Apache’s error log for the domain.