A web terminal for root. It’s the real shell on your server, inside the panel, with your session protected by a one-time token. Use it for quick admin tasks when SSH isn’t handy. Because this is full root access, treat it like a loaded power tool: precise, fast, and not forgiving.

What you can do here

• Run any shell command as root (software installs, service restarts, quick edits).
• Tail logs, check status, move files, and fix configuration without leaving the panel.
• Toggle fullscreen for focus; resize is automatic so the terminal stays readable.

How it works (in simple terms)

• When you open the page, the panel spins up a short-lived terminal listener for your session and hands your browser a one-time token to talk to it.
• If there’s no activity for a while, the connection is closed. You’ll see a Reconnect button.
• Each session is isolated to you and only created after you’ve authenticated to the panel as root.

Basic controls

• Fullscreen: click the expand icon in the header. Click again (or press Esc) to exit.
• Resize: the terminal auto-fits when you resize the window or switch fullscreen.
• Reconnect: if the socket closes (idle or network), the screen dims; hit Reconnect to reload a fresh session.

Good habits (and guardrails)

• Know where you are: commands run as root; a stray space in rm or rsync can ruin your week.
• Stage risky changes: prefer systemctl reload before restart where possible.
• Copy/paste carefully: multi-line pastes execute fast; consider drafting in an editor first.
• Logs are your friend: keep a second tab with Monitoring or journalctl -f while making changes.

Troubleshooting

• “No activity detected…” — Session timed out. Click Reconnect.
• Blank terminal / immediate close: check that your browser allows WebSockets and there’s no proxy or firewall blocking them.
• Fullscreen doesn’t work: some browsers block it on non-user actions; click the button again or press F11.

Security notes

• Only the root panel user can access this terminal.
• Each session uses a unique token, bound to your panel session and expiring on close.
• Idle sessions are terminated to reduce risk; re-opening creates a fresh, isolated session.