The current Terminal integration uses supported cPanel account SSH access. It is intended for the hosting account's permitted environment, not unrestricted root administration. Confirm the account's shell access and your product policy before enabling it.
IN THIS ARTICLE
01 Prepare the environment
- Verify that the cPanel account has the required SSH or shell capability and that your server policy permits customer access.
- Check outbound SSH connectivity from the WHMCS host to the hosting server.
- Confirm the required PHP libraries, command-line PHP and writable private storage are available for the selected terminal mode.
- Enable Terminal for the regular hosting product. On application plans, inspect the conditional tool availability and supporting server configuration.
- Open an active test service as a normal customer and run a harmless command that confirms the account identity and current directory.
02 Understand the connection trust
The integration manages encrypted SSH credentials or key material as configured and records the server identity when establishing trust. If the server's host key later changes, the connection is refused until the trusted profile is addressed.
Verify the reason for a host-key change with the server administrator, such as an authorised rebuild or migration. Compare the actual fingerprint through a trusted route before accepting a replacement. Do not reset trust merely to remove an unexplained warning.
03 Choose the appropriate mode
The normal command workflow has a bounded execution time. Advanced interactive mode provides a full terminal session where supported, with session count, lifetime and output limits. A long-running background administration task may need a different authorised operating procedure.
Do not describe the inactivity limit as exactly a period without typing. Session activity includes connection and polling behaviour. Close sessions after use and avoid leaving a privileged browser open on a shared computer.
04 Example: confirm the Terminal account without changing files
Open Terminal on an owned test service and run these read-only commands separately:
id -un
pwdid -un prints the effective account username. Compare it with the hosting username recorded for this service. pwd shows the current directory. It may be the account home or another permitted working directory, depending on the session; inspect the actual value rather than assuming every account uses the same path.
If the username belongs to another customer or is an unexpected privileged identity, close the session and correct the account mapping before running further commands. These checks establish the session identity and starting location. They do not prove every filesystem permission or application operation is configured correctly.
Does a Terminal command have automatic rollback?
Terminal commands can change or delete account data immediately. A command's output or exit status must be reviewed, and the relevant website or service should be tested afterward. AI Undo does not universally reverse shell commands.
Use an appropriate backup before significant work. Do not ask customers to paste database passwords, private keys or other secrets into commands that will be retained in command history or audit records.
05 Troubleshoot access
Check service status, product tools, account shell permission, paused account writes, SSH reachability and the host-key state. Verify the account username before changing credentials. Interactive mode also depends on the worker environment and private storage.
Audit records can identify commands and timing but are not a promise that every output stream is retained. Capture only the safe error details needed for support and close the test session when finished.