Terminal
Run account-scoped commands in the hosting environment.
1Overview
Terminal provides a shell limited to your hosting account, allowing supported maintenance and deployment commands without root access.
2Before you begin
User-panel actions affect only resources owned by the signed-in hosting account. This is an advanced task; schedule it carefully and keep a rollback path.
3Step-by-step workflow
Open Terminal, confirm the current directory and account, run one command at a time, and use standard output and logs to verify the result. Use the application interface for managed start and stop actions.
- Open Terminal from your hosting account and read its access status.
- Start the terminal only when you need a command-line task supported by your account.
- Check the current account and directory before running a command.
- Use the intended website or application folder and run one reviewed command at a time.
- Read the complete output and stop if the command targets an unexpected path.
- Keep passwords and API tokens out of command arguments and screenshots.
- Return to the relevant panel page to check any build, file, or application change.
- Disconnect the terminal when finished.
4Practical example
Example: use the terminal to inspect a project dependency or run an approved application command inside its own folder. Manage server services through provider or administrator tools.
5Verify the result
Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.
- Confirm the expected files, build result, or command output exist.
- Review logs if a command affects a website or managed application.
6Common problems and what to check
Terminal access is unavailable: your package or provider policy may not permit it.
Permission denied appears: check the selected directory and file owner rather than trying administrator commands.
A command is missing: ask the provider whether it is supported; downloading an unreviewed replacement can affect your account.
7Security, impact, and rollback
Commands can still delete your files or expose credentials. Avoid unreviewed scripts and back up before bulk changes.