Skip to main content
Use SFTP to transfer files over the instance’s SSH connection.

What you’ll need

  • An instance in Running.
  • The SSH hostname and username from its connection details in Compute.
  • The private key matching the public key supplied for the instance.
  • An SFTP client, such as the command-line sftp tool, WinSCP, or FileZilla.
The SSH endpoint uses port 22. Use the console’s username, which may differ from the image’s default user. Follow any additional SSH configuration supplied there.

Transfer files from a terminal

Replace the placeholders below with the console values and your private-key path:
If you already created an SSH config entry named hivenet, you can use sftp hivenet instead. At the sftp> prompt:

Connect with WinSCP or FileZilla

Create a new SFTP connection using: Use a private-key format supported by your client. If it requests conversion, use its supported key-import process or PuTTYgen. Never upload the private key to Compute. Only configure a proxy or jump host if the console’s connection instructions require one. Verify any host-identity prompt before accepting it; see SSH configuration and host verification. After connecting, use the local and remote file panels to upload or download files.

Transfer a folder with rsync

If rsync is installed on both computers, use it to copy a folder and retain partial transfers for a later retry:
Use a destination folder your SSH user can write to. Rerun the command after an interruption.

Troubleshooting

  • Permission denied: Check the username, private-key path, and matching public key on the instance.
  • Connection timed out or closed: Confirm the instance is Running, use the current console connection details, and check outbound port 22 on your network.
  • Host verification failed: Verify the host identity before changing saved trust settings.
  • The client rejects the key file: Check which key formats it supports and convert locally if needed.
If the problem continues, contact Support with the instance ID and error message. Keep your private key private.