SSH Terminal ​
SSH Terminal opens a command-line session for your hosting account in the browser, without a separate SSH client.
Location in Sidebar ​
Security > SSH Terminal
When the menu entry appears ​
The SSH Terminal entry appears only when your administrator has set up the following, which depends on whether the server runs CloudLinux:
| What to set up | On a CloudLinux server | On a server without CloudLinux |
|---|---|---|
| Terminal service | The Terminal module is installed. | The SecureBox service is installed. |
| Hosting plan | SSH Terminal is included in the feature list of your hosting plan. | Nothing to set. |
| Your account | SSH access is enabled (administrator: Accounts > Edit Account > Enable SSH Access). | SSH access is enabled (administrator: Accounts > Edit Account > Enable SSH Access). |
Terminal and SecureBox cannot run side by side. When SecureBox is installed, the entry appears for every account with SSH access, whatever the plan's feature list says.
Since panel 1.9.1, an account without SSH access does not see the entry at all. If the entry is missing, ask your administrator to set up the items above; the administrator's version of this list is in Giving an account owner the SSH Terminal.
Using the terminal ​
When the page opens, it checks the connection to the server first and then starts the session in the terminal area. Type commands as you would in an SSH session, for example:
- Move around and read your files (
ls,cd,cat). - Run your own scripts and command-line tools.
- Check your own running processes (
ps,top).
If a check fails, the page shows The terminal connection did not open. with the reason and the next step, and does not start the session. See Troubleshooting.
Security Notes ​
- The terminal follows your account's SSH access. When your administrator switches SSH access off, the entry disappears and the page no longer opens.
What you can see about other accounts ​
You are isolated from the other accounts sharing the server:
- Processes. Tools such as
psandtopshow only your own account's processes. Another account's running programs and their command lines, which can contain passwords passed as arguments, are not visible to you, and yours are not visible to them. - Files. Site and account directories carry restricted permissions that keep other accounts out of your home directory.
Both protections apply to new servers and are applied to every existing account when a server is upgraded. On an upgrade, the ownership of your files and the permissions of the files inside your home directory are left exactly as they were; only the account directories themselves are tightened.
Troubleshooting ​
- The terminal did not start. Your browser could not load the terminal from
cdn.jsdelivr.net. Allow that address in your browser, ad blocker, or network filter, then reload the page. - The terminal connection did not open. The message names the reason and the next step. If the session token is missing or expired, reload the page. When the step is for the server, for example the Terminal module is not installed or its service is not running, pass the message to your administrator.
- The connection drops or never opens. The terminal uses a secure WebSocket connection to the panel's address. A network or proxy that blocks WebSocket connections stops it from opening. The page names what happened and the next step.