SSH Protocols
SFTP and FISH Protocols
SFTP and FISH allow users to access, manage, and transfer files through a secure SSH channel. SFTP connects directly to a container through the platform SSH gateway, while FISH enables secure file-system management through supported file managers and FTP clients.
Protocol Overview
SSH key requirement
Both connection methods require a local private key that corresponds to a public SSH key previously added to the platform dashboard.
Connect through SFTP
The following example uses FileZilla, but another client with SFTP support can be configured using the same SSH gateway, port, user identity, and private key.
Prepare the Private SSH Key
Linux and macOS users normally receive the private key automatically when the SSH key pair is generated. Windows users must additionally save the private key that corresponds to the public key uploaded to the dashboard.
Add the Private Key to FileZilla
Start FileZilla and open Edit > Settings.
Open the SFTP section, click Add keyfile, and select the previously saved private SSH key.
Click OK to save the configuration.
Configure the SFTP Site
Open File > Site Manager.
Click New site and provide the connection details below.
gate.{hoster_domain}.
3022.
{node_id}-{user_id}.
The Node ID is available in the environment container list or through the SSH console. The User ID is the number shown before the @ symbol in the platform SSH connection string.
Click Connect. After authentication succeeds, the remote container folders appear in the FileZilla remote-site panel.
SFTP connection complete
You can now securely browse, upload, download, rename, and manage application files through the SFTP connection.
Connect through FISH
The following workflow demonstrates FISH access by establishing a secure connection between a remote container and Midnight Commander.
Verify the Private SSH Key
Confirm that the local computer contains the private key associated with the public SSH key uploaded to the platform dashboard.
The default file is usually located at one of the following paths:
Check the ownership and permissions of the private key.
For a DSA key, use:
Required key permissions
The key must be owned by your local username and should normally use permission mode 400 or 600. The connection can fail when other users can read the private key.
Configure Midnight Commander
Install and start Midnight Commander.
Press F9 to display the menu bar. Open the menu for the left or right panel and select Shell link.
In the Shell link to machine dialog, enter the container Node ID followed by the platform SSH connection string.
Click OK to establish the connection.
After the connection is established, the container file structure appears in the selected Midnight Commander panel.
FISH connection complete
You can now securely manage the container file system through Midnight Commander using shell-based file operations.
