Terminal in WHM — Simple, Safe, and Clear Guide
The Terminal gives you a shell right inside your WHM session—no separate SSH app needed. Use it for direct command-line work on the server.
Warning: Commands run here can break or disable your server. Only experienced users should use Terminal, and double-check every command before pressing Enter.
Open the Terminal
- Sign in to WHM as root (or a reseller with permission).
- Go to Server Configuration → Terminal.
- Read the warning message, then proceed to launch the shell.
What to Expect
- It runs an in-browser terminal attached to your current WHM session.
- Your usual shell profile (for example,
~/.bashrc) applies to the session. - It’s meant for quick administrative tasks; for long-running or risky operations, standard SSH is often safer.
Quick Examples
Useful, low-risk commands to verify the system state:
# system info
uname -a
uptime
df -h
# services (examples)
systemctl status httpd
systemctl status mariadb
# logs (examples)
tail -n 100 /usr/local/apache/logs/error_log
journalctl -xe --no-pager
Safety Tips
- Prefer read-only checks first (status, logs, disk usage).
- Test complex commands on a staging server before production.
- Keep another access path (SSH/console) available in case your session closes mid-change.
Troubleshooting
- If the terminal doesn’t load, refresh the page and ensure JavaScript is enabled.
- Confirm your user has permission to access Terminal.
- For persistent issues, use SSH while you investigate browser or network blocks.
Reference: “Terminal in WHM” documentation (accessing an in-browser terminal within a WHM session and the associated warnings).


