Product Setup

IBM Aspera Connect Server is a web-based file server that enables file access through a browser, and transfers files using the IBM Aspera Connect Browser Plug-in. Additionally, you can set up HTTP Fallback to establish HTTP- or HTTPS-based file transfers with clients that don't have FASP connectivity.

To install Connect 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 performs your upgrade automatically, Aspera highly recommends completing the tasks described in Before Upgrading or Downgrading. If you do not follow these steps, you risk installation errors or losing your configuration settings.
  3. Check what version of Perl is installed and upgrade if necessary.
    The Connect Server web UI requires Perl v5.10 or higher. To check what version is installed on your machine, run the following command:
    # perl -v

    Upgrade if required, installing Perl 5.10 or higher in the /opt/csw/bin directory.

  4. Change the path of the Apache user (or globally) to include /opt/csw/bin before /usr/bin.
    The Apache user is typically 'nobody'. Edit the .profile file in the home directory of the user so the PATH is the following:

    To change the global PATH (to apply to all users), edit the file /etc/profile, adding the same new PATH as for an individual user.

  5. Run the installer
    To run the installer, run the following commands with the proper administrative permissions. Replace the product version accordingly.
    # pkgadd -d /filepath/aspera-entsrv-version.pkg 
  6. For versions 9-11.2, install OpenSSH.
    Solaris 9 - 11.2 is installed with a version of SunSSH that is not supported by Aspera and you must install OpenSSH. See and your OS manual for instructions.

    Solaris 11.3+ SunSSH is supported.

  7. Install the license.

    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.

  8. Review or update OpenSSH authentication methods.
    Open your SSH Server configuration file from /etc/ssh/sshd_config with a text editor.

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

    PubkeyAuthentication yes
    PasswordAuthentication yes

    Save the file then run the following to reload SSH:

    # pfexec svcadm refresh ssh

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

  9. Troubleshooting
    If the installer freezes during installation, another Aspera product might be running on your computer. To stop all FASP transfer-related applications and connections, see Before Upgrading or Downgrading.
    If you receive the error message, "Current administration requires that a unique instance of the <ASPRent> package be created. However, the maximum number of instances of the package which may be supported at one time on the same system has already been met" this indicates that you have an Aspera package installed. Remove the exisiting package and install the new one by running the following commands:
    # pkgrm ASPRent
    # pkgadd -d /filepath/aspera-entsrv-version.pkg
  10. Set up your new Connect Server's web UI (or verify your web UI settings after an upgrade).
    Your IBM Aspera transfer product is now installed. Additional steps are required to configure the web UI, see Connect Server Web UI Setup.

Upgrade Follow up

  1. If upgrading and the Redis DB is run on another system: Update the KV store keys to the latest format.
    The local Redis DB schema is automatically updated by the installer, but non-local redis DB must be manually updated by running the following command as root:
  2. For all upgrades: Validate aspera.conf.
    The aspera.conf file is not overwritten during an upgrade and your configurations are preserved. However, the XML formatting, parameters, and acceptable values may have changed between your old version and new version. Run the following command to check aspera.conf for XML form and valid configuration settings:
    # /opt/aspera/bin/asuserdata -v