IBM Support

IBM Aspera Connect 3.9.8 FAQ



IBM Aspera Connect 3.8 (and older versions) does not work anymore.


  • Why did Connect stop working in Firefox?

The certificate for has been revoked. As a result, Aspera Connect 3.7 and 3.8 no longer work with Firefox and Safari. Users must update the web application that is integrated with Connect by upgrading to the Connect 3.9.x SDK. In addition, users must enable the corresponding web browser extension.

For more details, see security bulletin

  • When was Connect 3.9 announced?

Announcements for Connect 3.9 were first issued in early 2019. Aspera urged users to upgrade to Connect 3.9 by June of 2019. The initial release notes explained the upcoming changes for extensions. Aspera has provided:

  • Why was I not contacted?

  • Due to European privacy laws (known as GDPR), contact information cannot be stored or used without consent.
  • Our list of Aspera server administrators is incomplete. Often the contacts involved at the time of the original purchase are no longer involved with server administration.
  • If you wish to opt into critical product updates, please submit a list of contacts to: Soon customers will be able to configure "IBM My Notifications" through support portal
  • Why does Connect 3.9 use extensions?

Google Chrome, Mozilla Firefox, Microsoft Edge are updated very frequently with security fixes. Aspera needs to continue to support browser integrations. Over time, browsers have restricted the options for desktop integrations. For example, Java applets, NPAPI plugins, and mixed HTTPS/HTTP content are no longer viable options. Web extensions are the new industry standard for reliable browser to desktop communication.

Web extensions deliver a better overall user experience. For more information, see

  • My server is in a locked-down environment. How does the Connect 3.9 change affect me?

By default Aspera web applications are configured to load the Connect SDK from Cloudfront. When a user visits Faspex/Shares, the application accesses and loads Connect Javascript components over the Internet. However, Aspera web applications can also be configured to host Connect javascript locally.

See "Locally host Connect" and "Lock Connect SDK version" in

  • How can I tell which SDK my web application is using?

  1. Open the Network Inspector (
  2. Filter for "asperaweb-4.js"
  3. Check which URL it is being served from. The URL  is the latest version (subject to updates).
  4. Open the URL in a new tab to see version details.
  • How can I use a specific version of Connect SDK that won't change?

Use 3.8.3:
Use 3.9.8:

  • What if my users cannot upgrade to Connect 3.9? They don't have permissions to install. The installation does not succeed.

You can configure your web application to use an older version of the Connect SDK for partial browser support:
  • Try all the browser options available to you. Some browsers may still work with Connect 3.8. Internet Explorer is currently unaffected by the extension migration.

  • How can users get the extension if they cannot access the internet?

Deploying extensions for closed environments is documented by

The latest Chrome CRX and Firefox XPI files are:

Video demo:

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSXMX3","label":"IBM Aspera Connect"},"Component":"IBM Aspera Connect","Platform":[{"code":"PF017","label":"Mac OS"},{"code":"PF033","label":"Windows"}],"Version":"3.9.8","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
20 February 2022