DuskShell
Register

Documentation

DuskShell Docs

Operational documentation for everyday server maintenance. Find guides by task: connection, commands, files, diagnostics, security, account, and billing.

AccountPricingContact support

Getting started

Add a server and understand the workspace.

Add your first server

Prepare host, port, username, and authentication method. After saving the connection, DuskShell opens a workspace with terminal, status, files, and tools in one place.

  • Confirm SSH login is enabled.
  • Prefer key authentication; passwords are better kept for temporary or low-risk environments.
  • Name connections by project, environment, and region.

What the workspace includes

After connecting, check server status first, then move to terminal, files, commands, Docker, Nginx, or logs. The terminal remains the core surface; panels reduce repeated command lookup and path copying.

  • Resource status helps identify CPU, memory, disk, or network issues.
  • The file panel supports upload, download, editing, and server-to-server transfer.
  • Service entries appear only after matching components are detected.

Connection and auth

SSH failures, reconnects, and key problems.

SSH connection failed

Connection failures are rarely a client-only issue. Check the network path first, then authentication.

  • Confirm the server is online and the host and port are correct.
  • Check security groups, firewalls, and fail2ban.
  • Confirm username, password, or key matches the target server.
  • Reconnect attempts during a server reboot are expected until the OS is back online.
ssh -vvv user@host -p 22
nc -vz host 22

Key authentication failed

Key issues usually come from format, passphrase, server-side authorized_keys, or permissions. DuskShell stores connection profiles but does not bypass SSH rules.

  • Confirm the private key and passphrase.
  • Check ~/.ssh/authorized_keys on the server.
  • Confirm sshd_config allows PubkeyAuthentication.
  • Never paste private keys into chat or support email.
chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

Commands and AI

Command templates, log explanations, diagnostics.

Command templates

Common maintenance actions can start from the command panel, so you do not have to search for flags every time. DuskShell still shows the command before execution.

  • Useful for logs, ports, large files, processes, and disk checks.
  • For delete, overwrite, restart, or stop actions, confirm scope first.
  • Templates support the terminal; they do not replace it.
journalctl -u nginx --no-pager -n 100
find /var/log -type f -size +100M -print

AI diagnostics

AI helps explain logs, outline troubleshooting paths, and draft commands. It reduces lookup time but should not replace production change review.

  • Use it for logs, service status, and command output.
  • Do not enter passwords, private keys, tokens, or sensitive customer data.
  • Read generated commands before running them.

File management

Upload, download, edit, and transfer files.

Upload, download, and edit

The file panel is for configs, logs, deployment scripts, and site directories. The online editor is for small changes; larger changes should still go through version control.

  • Back up nginx.conf, .env, and docker-compose.yml before editing.
  • If upload fails, check directory permission, disk space, and SSH user permissions.
  • For large files, keep the connection stable or use server-side tools.

Server-to-server transfer

Use server transfer for logs, backups, and release artifacts. Confirm source path, target path, file size, and available disk space before starting.

  • Do not move production keys, database dumps, or customer data to unnecessary servers.
  • Verify file size or checksum after transfer.
  • Confirm target directory contents before overwriting.

Service tools

Docker, Nginx, and logs.

Docker panel

Docker is a supporting tool inside the workspace. It helps inspect container status, ports, images, and logs when diagnosing service issues.

  • Check exit code and logs before restarting repeatedly.
  • Confirm recoverability before removing containers, images, or volumes.
  • For deployment issues, inspect env vars, mounts, and networks.
docker ps -a
docker logs --tail 100 <container>

Nginx panel

The Nginx panel helps inspect site config, logs, certificate paths, and reverse proxy problems. It is a troubleshooting entry, not a mandatory site management system.

  • Validate syntax before reload.
  • For 502/504, check upstream service, ports, container network, and timeout settings.
  • HTTPS issues usually involve certificate chain, DNS, or listening ports.
nginx -t
tail -n 100 /var/log/nginx/error.log

Account and security

Membership, device authorization, deletion.

Membership and device authorization

Your DuskShell account is for website sign-in, membership, and device authorization. It is not your SSH user. If the device limit is reached, revoke old devices in account center.

  • Membership status, billing cycle, price, and benefits come from the backend.
  • Web, desktop, and mobile clients may each consume device authorization.
  • If status looks wrong, refresh account center and confirm the signed-in account.

Account security

Changing your DuskShell account password does not change server passwords, SSH keys, or remote host configuration.

  • You can sign out other devices when changing password.
  • Deleting an account affects sign-in, membership, device authorization, and sync data.
  • For billing or deletion issues, use account center or contact support.

Need support

Include your operating system, DuskShell version, server OS, error message, and what you have already tried. Do not send passwords, private keys, tokens, or full production configs.

[email protected]