Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > SSH connections in FTP Voyager

SSH connections in FTP Voyager

Updated April 20, 2017


This article gives an overview of how FTP Voyager uses SSH connections and provides steps to configure SSH authentication using public/private key pairs.


All Serv-U versions


The Secure Edition of FTP Voyager supports SSH encryption. This option is enabled under the Advanced > Security menu of your FTP site profile.


When FTP Voyager uses SSH encryption, the log looks different from a traditional connection. The following is an example of an SSH login:

STATUS:> Connecting to "" on port 22.
SSH Server Version: SSH-1.99-OpenSSH_3.4p1 Debian 1:3.4p1-1
Server --> Client encryption: 192 bit aes-cbc
Client --> Server encryption: 192 bit aes-cbc
Selected public key protocol: ssh-dss Compression: NONE
STATUS:> Login successful
STATUS:> Getting current folder
Current folder: /home
STATUS:> Setting transfer mode to ASCII
STATUS:> Listing contents of: /home
Listing complete: /home
STATUS:> Resolving links
STATUS:> Resolving symbolic link: /home
STATUS:> Resolved 1 link into 1 folder and 0 files 


Note: SSH encryption usually uses port 22. This can make traffic pass through firewalls easier. Verify that nothing is blocking port 22 for the connection to complete.

Configure SSH authentication with public/private keys

FTP Voyager also supports the use of a public/private key pair for SSH authentication. This method is used when connecting to Linux systems. To configure authentication using SSH keys, perform the following steps:

  1. Go to View > Options > SSH Options.
  2. Select the Use public key authentication option to enable authentication using a public key.
  3. Select Browse for the Private Key, locate and select the appropriate directory. FTP Voyager automatically finds the public key if it is located in the same directory.
  4. If the private key is password protected, enter the password used to protect your private key. Otherwise, clear the Use private key password option.
  5. If compression causes errors when trying to connect or transfer data, the Use Compression option can be cleared.
  6. Click OK.

Create a public/private key pair

Note: FTP Voyager currently does not support configuration of key pairs for individual site profiles.

In FTP Voyager, you can create a public/private key pair if one has not already been issued to you.

  1. Click Create New Key Pair Files.
  2. Select the Key Type. Unless your server administrator has indicated that you need to use RSA, use the default type DSA.
  3. Select the Key Length. If more security is required, select 2048 or 4096 from the drop-down list if your server supports it. The longer the key, the slower the transfer will be.
  4. Enter the Private Key Password. This password is used to protect the private key. It should be alphanumeric and at least six characters long.
  5. Select the Public Key File Format. This can be set to SSL unless your server administrator requires you to use SSH or OpenSSH.
  6. Enter the location of the public key and private key. This can be any directory.





Last modified