IBM Aspera Connect common issues

Edit online

Aspera on Cloud requires one of two transfer methods to power high-speed transfers between user desktops and Aspera transfer servers. Users can either download and install Aspera Connect, a free, lightweight, install-on-demand software program; or an admin can configure the IBM Aspera HTTP Gateway and attach it to your Aspera on Cloud organization.

Aspera Connect is the default transfer method for Aspera on Cloud and other Aspera web app. However, if your deployment of Aspera on Cloud does not allow users to download and install client software, an admin can configure an alternative transfer method: the IBM Aspera HTTP Gateway. The Aspera HTTP Gateway is a standalone product that uses both HTTP/S and Aspera FASP to complete file transfers.

For troubleshooting the installation of IBM Aspera Connect, see Installation troubleshooting.

IBM Aspera Connect powers high-speed transfers between desktops and Aspera servers. Once installed, Connect runs automatically runs in the background for each upload and download you initiate using Aspera on Cloud.

When you first log in to Aspera on Cloud, the app prompts you to download and install Aspera Connect. The installation is an easy, two-step process in most browsers; Aspera on Cloud guides you through the process. The first guidance dialog looks something like this:

Install the Connect app once; Install the Connect extension for each browser

There are two components of IBM Aspera Connect; you must install both components as follows:
  • The Connect application, which you install once on any computer you use to access Aspera on Cloud.
  • The Connect browser extension, which you install on each browser you use to access Aspera on Cloud.
For detailed installation procedures, see Installation.

Allow the connection for each transfer server

When you start a transfer that requires Connect, Connect displays a dialog requesting permission to connect with the relevant Aspera transfer server.

Connect displays this dialog for the transfer server relevant to each transfer you initiate. Depending on the location of your content, your recipients, and those who send to you, your transfers may involve multiple transfer servers. Connect requests your permission to connect with each server. You must grant permission to allow the transfer to proceed.

Connection request dialog from Aspera Connect.

The exact wording of this dialog may vary depending on your browser. But in any case, IBM Aspera highly recommends that you check the option to allow all connections with the host, or always allow. Otherwise you must manually allow each transfer to initiate. If this dialog displays behind another application window, blocked from your immediate view, you may not realize that Connect is requesting your permission; without your permission the transfer cannot start.

Already installed Connect, but still being prompted?

There are two circumstances in which you may continue to see the installation dialog even though you've already installed Connect:
  • There is a new version of Connect available, and the app prompts you to install the upgrade.
    In this case, you must download and install the Connect app upgrade. You may or may not need to update your browser extension; the installation process will guide you.
  • You have not installed the Connect extension in your current browser.
    You may have installed the extension in a different browser, but the extension is required for each browser. In this case, there is no need to reinstall the Connect app, but you must install the browser extension.

To contact your local tech support administrator, click in the banner and select "Technical support".