Product Setup

Important: If this is a product upgrade, review all prerequisites described in "Before Upgrading."

To install Enterprise Server, log into your computer with root permissions, and follow the steps below.

  1. Download the IBM Aspera product installer.

    Use the credentials provided to your organization by Aspera to access:

    If you need help determining your firm's access credentials, contact your Aspera account manager.

  2. For product upgrades, ensure you have prepared your machine to upgrade to a newer version.

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

  3. Run the installer

    To run the installer, use the following commands with the proper administrative permissions. Replace the file name accordingly.

    OS Commands
    $ rpm -Uvh aspera-entsrv-version.rpm 
    $ dpkg -i aspera-entsrv-version.deb
  4. Install the license.

    The license can be installed in two ways: through the GUI or via command line. See the table below for instructions.

    Method Instructions
    GUI To install the license via the GUI, run asperascp in Terminal as a root user to launch the application. If this is a fresh install, an Enter License window appears. Either click Import License File and select the license file, or click Paste License Text to copy-and-paste the license file's content. The license information will appear in the window. Verify that it is correct and click Close.
    The Enter License window.
    Terminal To install the license from the command line, create the following file:
    Copy and paste your license key string into it, then save and close the file. To verify the license information, run the following command:
    $ ascp -A

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

  5. Review or update OpenSSH authentication methods.

    Open your SSH Server configuration file with a text editor:


    To allow public key authentication, set PubkeyAuthentication yes. To allow password authentication, set PasswordAuthentication yes, for example:

    	 						PubkeyAuthentication yes
    	 						PasswordAuthentication yes

    The System Integrity Protection feature in Mac OSX 10.11 (El Capitan) or macOS Sierra blocks SSH-based services, which are required for Aspera transfers. Make the following changes to enable Aspera services. In the sshd_config file, uncomment the setting PermitUserEnvironment and change the value to yes.

    Save the file then run the following to reload SSH:

    $ sudo service sshd restart
    $ sudo /etc/init.d/ssh restart

    To further secure your SSH Server, see Securing your SSH Server.

  6. If you are upgrading from product version 2.2 or earlier, manually convert the old aspera.conf file.

    For product versions 2.5+, the docroot settings are automatically moved to the Aspera configuration file, aspera.conf. If you are upgrading from product version 2.2 or earlier, the installer converts your old configuration files to the new format, using a "strict" method. The conversion will fail if the old aspera.conf has errors or unrecognized directives. To review and convert aspera.conf manually, first move it if it is not in the default location /opt/aspera/etc. To review any errors, run a strict conversion manually.

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

    If an error occurs during the conversion, use the relaxed conversion method:

    $ cd /opt/aspera/etc
    $ sudo asconfigurator -F convert_conf_V1_data ./aspera.conf 
  7. (For upgrades) Check aspera.conf for errors

    When upgrading your Aspera product to a newer version, Aspera recommends that you check aspera.conf for errors. To validate aspera.conf, run the following command in a Terminal window:

    $ /opt/aspera/bin/asuserdata -v 
  8. For upgrades from 3.5.6 or earlier, update the KV store keys to the latest format.
    Run the following command as root:
    # /opt/aspera/bin/asnodeadmin --db-update
  9. Troubleshooting
    Important: When upgrading from Connect Server versions older than 3.0, system-level security settings are not preserved and must be reconfigured. For instructions on enabling or disabling system-level security, see "Configuring Apache".