টার্মিনাল

Free plugin. A command line in the browser. Root gets the server shell in the Host Manager; each hosting account gets a shell inside its own home folder in the hosting panel.

For the customer

Advanced → Terminal in the hosting panel. The page shows a black console with a prompt such as demo@example.com:~$. Type a command and press Enter.

• The up and down arrows walk through the history.
• cd works, and the prompt shows the folder you are in.
• Clear the screen with the clear button.
• Commands run as the account's own user, so they can only read and write what that user may.

The tool needs the account to have the Terminal feature in its feature list, and the host must have it switched on (see below). Otherwise the page says Your host has switched the terminal off or The terminal is not included in your hosting package.

An account with shell access in its package can also use SSH (see Security → SSH Access). The Terminal does not need SSH or a key; it works through the panel.

For root

Server Configuration → Terminal (shell) opens a console that runs as root on the server. It is the same as an SSH session as root, so treat it with the same care: a wrong command can break the server. Use it for a quick df -h, journalctl or systemctl status, and for aiohpanel commands. See The APIs and the command line.

Resellers do not get the root terminal.

Settings

Plugins → Manage Plugins → Terminal → Settings:

To allow it for some accounts only, switch it on here and take Terminal out of the feature list of the other packages, under Packages → Feature Manager.

On a demo host

The Demo driver cannot run a real shell, because that would give a visitor the machine. The Terminal therefore allows a short list of safe commands: ls, dir, pwd, whoami, date, echo, cat, head, tail, wc, du, df, uname, hostname, env, id, uptime, find, grep and php (only php -v, --version, -m and --ini). Root's demo terminal stays inside the data folder. Chaining with ;, |, &&, backticks or $( ), and redirection with >, are refused. Paths that leave the account's folder are refused with permission denied (outside your folder). On a Linux server none of this applies; the commands run for real as the account.

Safety notes

• The console runs in the account's home as that user, never as root, for accounts.
• Each command is sent on its own and ends when it finishes; there is no program that keeps running in the background, so top or an editor like nano will not work.
• Long jobs (a big composer install, a tar of many gigabytes) are better run by a cron job from Advanced → Cron Jobs than in the Terminal.
• Every command typed is written to the activity log with the user's name.

If you do not want any shell in the browser on a server, leave the plugin switched off.