Download the installer from the link below. Use the credentials provided to your organization by Aspera to access:

If you need help determining your firm's access credentials, contact Technical Support.

Although the Aspera Connect Server installer performs your upgrade automatically, we highly recommend completing the tasks identified in the topic "Before Upgrading." If you do not follow these steps, you risk installation errors or losing your former configuration settings.

When downloaded, run the installer using the following commands and with the proper administrative permissions. Replace the file name accordingly.

$ rpm -Uvh aspera-entsrv-[version].rpm 

$ dpkg -i aspera-entsrv-[version].deb

There are two ways to install the license: through the GUI or via command line.

Method	Instructions
GUI	To install the license via the GUI, execute asperascp in a Terminal (as a root user) to launch the application. If this is a fresh install, an Enter License window will appear. You may click the Import License File... and select the license file, or Paste License Text... to copy-and-paste the license file's content. When finished, the license information will appear in the window. Verify that it is correct and click Close.
Terminal	To install the license through command line, create the following file and paste your license key string into it: /opt/aspera/etc/aspera-license When finished, save and close the file. Use this command to verify the license info: $ ascp -A

If you are updating your product license after the installation, refer to Updating Product License.

Open your SSH Server configuration file with a text editor:

/etc/ssh/sshd_config

To allow public key authentication, set PubkeyAuthentication yes. To allow password authentication, set PasswordAuthentication yes. Here is a configuration example:

...
PubkeyAuthentication yes
PasswordAuthentication yes
...

When modified, execute the command to reload SSH:

$ sudo service sshd restart

$ sudo /etc/init.d/ssh restart

To further review your SSH Server's configuration to strengthen security, refer to Securing your SSH Server.

For product versions 2.5+, the docroot settings have been moved to the Aspera configuration file, aspera.conf. When upgrading from product version 2.2 or earlier, the installer converts your old configuration files to the new format, using a "strict" method. If the old aspera.conf file has errors or unrecognized directives, the conversion will fail. To review the errors, run a manual strict conversion. Change aspera.conf's path if it is not in the default location.

$ cd /opt/aspera/etc
$ sudo asconfigurator -T -F convert_conf_V1_data ./aspera.conf

If error occurs during the conversion, use the relaxed conversion method.

$ cd /opt/aspera/etc
$ sudo asconfigurator -F convert_conf_V1_data ./aspera.conf 

When upgrading your Aspera product to a newer version, it is recommended that you check the aspera.conf configuration file for errors. Run the following command in a Terminal window to validate aspera.conf:

$ /opt/aspera/bin/asuserdata -v 

At this point, your Aspera transfer product is installed; however additional steps are required to configure the Web UI. Please continue to the Chapter "Connect Server Web UI Setup" and review the topics contained herein.