SSH Terminal

Prerequisites

SSH Terminal is available only when both conditions are met:

1. The server provides an isolated SSH environment. On CloudLinux servers this is handled by the BoltTerminal module (listed as Terminal on the Modules page), which runs each user's shell inside CageFS. On servers without CloudLinux, the SecureBox service provides the isolated SSH environment (administrator: Services page).
2. SSH access is enabled for your hosting account (administrator: Accounts → Edit Account → Enable SSH Access).

If the menu entry is missing, contact your administrator to enable SSH for your account.

Overview

The SSH Terminal in AdminBolt provides direct command-line access to the hosting server through a browser-based terminal interface. It enables administrators to perform advanced system-level operations without using an external SSH client.

Key Features

• Shell Access: Execute commands directly on the server.
• No Client Required: Access terminal through any modern web browser.
• Secure Environment: Access limited by user role and impersonation context.
• Live Feedback: See real-time command output and logs.

Interface Description

Element	Description
Prompt Display	Shows current user and host info (e.g., user@server)
Input Field	Accepts Unix/Linux shell commands
Live Output Window	Displays results of executed commands

Location in Sidebar

Security → SSH Terminal

Use Cases

• Restart services (e.g., sudo systemctl restart nginx)
• Tail logs (e.g., tail -f /var/log/secure)
• Check server load (top, htop)
• Manage packages (yum, dnf, apt)
• Navigate the file system (ls, cd, cat, etc.)
• Run custom scripts or commands

Security Notes

• Only accessible to users with proper permissions.
• All sessions are logged.
• Always use caution when running commands via terminal, especially as root.

What you can see about other accounts

You are isolated from the other accounts sharing the server:

• Processes. Tools such as ps and top show 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

If the terminal does not load:

• Ensure browser supports WebSockets.
• Check if server's SSH and WebSocket daemons are running.
• Verify that impersonation or root permissions are correctly set.