IBM Aspera Faspex Application 3.9.3 Release Notes
IBM Aspera Faspex 3.9.3 Release Notes

IBM Aspera Faspex 3.9.3 Release Notes

  • Product Release: September 11, 2015
  • Release Notes Updated: April 1, 2016


This release of the IBM Aspera Faspex 3.9.3 for Windows and Linux provides the new features, fixes, and other changes listed below.

New Features

  • IBM Aspera Connect Browser Plug-In: Faspex 3.9.3 requires Connect 3.6.1. You are required to install or upgrade to Connect 3.6.1 for all browsers.
  • Drag-and-Drop for Google Chrome: The drag-and-drop functionality on the New Package page is now supported in Chrome. Users must use Connect version 3.6.1 or higher to use drag-and-drop in Chrome.
  • Direct Upload to Custom Inbox: For dropboxes, there is now an option to upload packages directly to a custom inbox without going to the default inbox first.
  • Cloud Referencing: When the source and destination of a package are in the same cloud storage, package files will link to the source files instead of making copies of the source files. This feature supports any cloud service that supports trap links.
    Note: The cloud referencing feature requires cloud storages that use IBM Aspera Enterprise Server 3.6.0+ to work.
  • Rake Tasks: The rake packages:clean_deleted command now cleans deleted packages in batches, instead of as a single query.
  • Security: Aspera common components (including OpenSSL and Apache) are now updated to increase security and protect against the logjam threat.
  • Cloud Storage: Faspex API changes now enable compatibility with Microsoft Azure file storages for IBM Aspera clients (IBM Aspera Drive, IBM Aspera Cargo, and IBM Aspera Add-in for Microsoft Outlook).
    Note: To make transfers with the IBM Aspera Add-in for Microsoft Outlook running Faspex 3.9.3 for Microsoft Azure, the Outlook Add-in must be upgraded to 1.3.4+ and you must have Connect Browser Plug-in 3.6.1+ installed.
  • Cloud Storage: The Faspex API now returns the "Paths" array differently to support cloud storage.


#32477: When downloading a file from a custom inbox with a filepath that does not exist on the default inbox, the download fails.


IBM Aspera Enterprise Server/Connect Server: A licensed version of 3.5.x or higher.
IBM Aspera Connect Browser Plug-In 3.6.1 or higher.

Red Hat 6-7, CentOS 6-7, SLES 11
Aspera Common Components 1.1.21+

XP, 2003, 2008, 2012

Internet Explorer 8-11, Firefox 27-44, Safari 6-9, Chrome 40-48
(Faspex users can successfully access Faspex from any of these browsers on any OS, as long as the browser and
OS are also supported by Connect)


Faspex supports the dragging and dropping of files and folders for transfer on a client; but this support varies by platform and browser. See the table below for details on how this release of Faspex supports drag-and-drop in your environment:

Browser Windows Client Mac OS X Client Linux Client
Firefox Files and folders Files and folders Drag-and-drop not supported
Chrome Files and folders Files and folders Drag-and-drop not supported
IE 8 and 9* Files and folders
IE 10 and 11* Files
Edge* Drag-and-drop not supported
Safari Files and folders

* Internet Explorer is limited in support for drag-and-drop because of how it records drop events. Edge does not support drag-and-drop from the system into the browser. For further information, see


md5: 2815b09866a0577c925cb11d8e76e339
sha1: 2f8443e308099a67ffe27d4ba11b1c2ef58c031f

md5: df10a54d578e421f904ad374e4cd157a
sha1: 1f8aba41e58bdafbbb4d214d389e396a83bf0aa5

Aspera Common Components:
md5: 153a87786e91c4100a70cdb38f53787b
sha1: 8fb02ee1645fc098e21b5d8aef72b6bc7824cf54


#31212 - (Linux Only) Upgrading the common components from older versions of 1.1 to any newer version deletes the /usr/bin/asctl symlink. Workaround: Installing Faspex after upgrading the common components will recreate the missing link during the installation process.

#31276 - Admins can no longer view regular users' packages by using the /aspera/faspex/sent/{id} REST resource

#32117 - Modified email notification template to show the link expiration date does not result in an email that shows the link expiration date.

#31141 - MySQL does not recover and reconnect when the connection is lost to a killed process. Background jobs continue to run with errors. Workaround: Restart the email background job by running asctl faspex:email:restart

#29531 - (Linux Only) Stats-collector displays an error when working with nodes that are configured for tlsv1.1. The Linux version of Faspex only works with SSLv3 or tlsv1.2.

#13835 - Faspex cannot connect to an AWS mail server using TLS; however, SSL connects successfully. This is relevant to the settings under Server > Notifications > E-mail Configuration.

#29547 - (Windows Only) Faspex displays an SSL error when adding a node with ssl_protocol set to tlsv1.1 or tlsv1.2.

#27371 - ADFS SAML users running Chrome 36.0 on a Windows machine are currently unable to login. Workaround: Use a different browser to login as an ADFS SAML user.

#25002 - Bad display on IE 9 for overlay of Connect on the Faspex New Package page. Workaround: This is an IE issue, you should upgrade to the latest browser version supported on your platform or ensure that you have the latest IE updates applied.

#21984 - On Centos 6.0 & 6.2, after installation and asctl faspex:setup has run and completed, users may see an invalid license message appear on the login page, even if they have copied over the correct aspera-license file to their /opt/aspera/etc directory.

#17652 - For an existing Faspex DS group: If this group is moved to another Organizational Unit (OU) on the DS server, and then the group is synced on Faspex, the group will become invalid on Faspex.

#17089 - After restoring Faspex 3.X from a source server, the destination server may or may not be able to verify the SSL certificates presented by a node (depends on whether the source server had a valid cert file or if it was missing altogether). Administrators should check to see if the cert.pem file exists and back it up prior to restoring.

#17011 - Safari on Mac downloads the Faspex backup file to a tar file. Users can change their Safari preferences so that archive files aren't automatically unzipped.

#16519 - (Linux Only) Some Faspex configuration settings (e.g. those that require system changes or asctl modifications) will not be restored when using the Faspex “Save/Restore” UI feature. For example, if the "Systemuser" flag is changed in faspex.yml, and the configs are backed up and restored to a new instance, the application will not start because the user must be created on the new instance with appropriate permissions. Another example is the "uri_namespace," which - if changed before a backup - must be updated in Apache using the "uri_namespace" command upon restoring. Other settings in faspex.yml include "HTTPPort", "HTTPSPort", etc, which will be overwritten to the previous values and may require manual steps toe ensure the ports can be used.

#16846 - If you are upgrading from Faspex 2.X and the transfer server is already set up on a different server, asctl will not handle this case. Please contact Aspera Support for assistance.

#16715 - If you set an alternate address (Server > Configuration > Web Server) on your source server and save your Faspex db+config folder (Server > Configuration > Save/Restore), then upon restore to a new server/instance, the alternate address will still be set on the new server. Subsequently, your email notifications will include an alternate address link to an instance which may not be up and running.

#16520 - If you download the Faspex db+config folder (from Server > Configuration > Save/Restore), the file will be saved to the browser's default location.


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.