Skip to content

Root Terminal

Run carefully scoped server commands from the administrator panel.

1Overview

Root Terminal is privileged server access. Commands run with administrator authority and can alter all accounts, services, and data.

Root terminal requires administrator verification. This example stops at the verification prompt; no command is running.
Root terminal with an administrator identity verification dialog and password field before command access is granted.

Root terminal requires administrator verification. This example stops at the verification prompt; no command is running.

2Before you begin

Administrator actions can affect multiple customer accounts and server services. This is an advanced task; schedule it carefully and keep a rollback path.

Prepare an approved command, target paths, expected output, backup, and rollback procedure before opening the terminal.

3Step-by-step workflow

Open Root Terminal, confirm the command and target paths, run one reviewed command at a time, and keep the displayed output with the change record. Prefer panel controls for routine service operations.

  1. Open Root Terminal only with a specific server-maintenance task and recovery plan.
  2. Confirm the server identity and current directory before typing a command.
  3. Review the command, target paths, expected output, and required backup.
  4. Run one command at a time and read the full result before proceeding.
  5. Avoid pasting unreviewed commands from messages, websites, or support tickets.
  6. Keep passwords, private keys, and API tokens out of command arguments and shared screenshots.
  7. Verify the resulting service or file change from its normal panel page or a separate connection.
  8. Close the terminal when the task is complete and retain the maintenance record.

4Practical example

Example: checking a service status is a read-only diagnostic task. Stopping that service, replacing its configuration, or removing its data is a different operation and needs a clearly understood impact and recovery path.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Use the appropriate panel page or service check to confirm the intended result.
  2. Keep the rollback command available until production validation is complete.

6Common problems and what to check

The terminal will not connect: check session expiry, access permissions, and terminal-service readiness.

Permission or path errors appear: verify the exact target before trying another command.

The output is unexpected: stop and investigate; do not continue a pasted sequence that assumes the earlier command succeeded.

7Security, impact, and rollback

Never paste unreviewed commands, credentials, or destructive recursive operations. Take a backup and state the rollback method before changing production configuration.

Related guides

Monitoring and ServicesInspect resource metrics and safely control managed services.Malware CenterRun, review, and act on server-wide malware findings.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area