Skip to main content
SSH gives you a shell inside your own sandbox container for WP-CLI, file inspection, and one-off commands. It does not provide access to the host, other tenants, or port forwarding. The SSH Access panel on a sandbox detail page

​
Fastest route: the CLI

The CLI turns on access for the sandbox and handles a short-lived session credential for you.
You need a ready, account-owned sandbox on a paid plan. The CLI requires OpenSSH; use Mount a sandbox when you want the files to appear as a local directory.

​
Use the dashboard

Open Site settings and select SSH Access, then turn access on for that sandbox. The panel provides the exact customer connection details, shows the host-key fingerprint for verification, and lets you manage account-level public keys. Only add public keys to SandyWP. Keep private keys private, revoke unused keys promptly, and turn SSH off when the sandbox no longer needs it.

​
Limits and safety

SSH sessions have idle, duration, concurrency, and connection-rate limits. If a session ends, reconnect and make long-running work resilient to interruption.
If the SSH panel says Not available, the service is not enabled for that sandbox’s region yet. The File Manager remains available for browser-based file work.
Use File Manager for no-client file editing, or Database for database work.