SSH Access & Remote Development
Connect only when your device or deployment explicitly supports an authorized SSH account.
SSH availability depends on the product, operating system and deployment configuration. Website account access does not create a device shell account, and this guide does not define a shared THOX username or password.
Confirm SSH is supported
Ask the device administrator or consult the release guide for the hostname, port, authorized username and authentication method. Do not enable a new network service solely because a generic support page mentions SSH.
Connect with the provided details
Replace the placeholders below with the administrator-provided values. Verify the server host-key fingerprint through a trusted channel before accepting it.
Do not bypass host-key checks when a key changes. Confirm whether the host was rebuilt or its key rotated before reconnecting.
ssh -p PORT USER@HOSTUse your authorized key
Use the authentication method configured for the deployment. When public-key access is supported, give the administrator the public key through the agreed process and keep the private key private.
Use a separate account and the minimum access needed. Agent forwarding is not required for a basic SSH connection; do not enable it by default.
Configure remote development carefully
After basic SSH access works, configure a compatible development client with the same host and account. Confirm which extensions, tools and processes it will install or run remotely.
Forward ports only when the deployment permits it, and keep them bound and authenticated appropriately. Do not expose a local inference or admin service publicly as a shortcut.
Collect a useful failure report
Distinguish name resolution, connection timeout, host-key verification and authentication errors. Record the error and time, then consult the administrator.
Never attach private keys, passwords or session tokens to a support request. Use the network troubleshooting guide if the service cannot be reached.