IBM Aspera Faspex Application 3.9.1 Release Notes
IBM Aspera Faspex Application 3.9.1 Release Notes

IBM Aspera Faspex Application 3.9.1 Release Notes

  • Product Release: March 5, 2015
  • Release Notes Updated: March 5, 2015


This release of the IBM Aspera Faspex Application 3.9.1 for Windows and Linux provides the following new features:

  • Microsoft Azure: Functionality for using Microsoft Azure transfer servers has been added. Administrators can also choose Windows Azure or Windows Azure SAS as the storage type when adding new nodes to file storage.
  • Installation: (Windows Only) Faspex Windows installer supports using Managed Service Accounts (MSA) for installation.
  • Accounts: New "locked" status in the Accounts page to describe accounts that are locked out from too many failed login attempts.
  • Dropbox: Dropbox members can submit packages to their dropboxes even without regular upload permissions. Users without overall "Upload" permissions do not have access to the "Normal Package" button. If they are members of dropboxes, they will be able to send to their dropboxes from the "New Package" dropdown, but if they are not members of any dropboxes, they will not see the "New Package" button at all.
  • Email Notifications: Email sending has been moved to a separate background service.
  • Transfers: Semi-colons are now acceptable delimiters in package recipient list.
  • SAML: SAML log out page redirects to local log out page to be more convenient.
  • Mobile/SAML: Faspex mobile clients can now authenticate with SAML credentials.
  • Console: To support importing user fields into IBM Aspera Console reports, user profile fields of a Faspex sender are now visible as tags in the transfer details of an upload or download.
  • Connect: Default IBM Aspera Connect Web Plug-in minimum version set to 3.1.4. Note that versions before 3.4.2 can still be used but may not be fully functional.
  • Connect: Ability to perform local Connect Web Plug-in installation.


#29623 - (Windows Only) In some cases, when upgrading to Faspex 3.9.1, the Apache HTTPD and MySQL Servers are set to Manual, not Automatic mode.

#29741 - Users can browse the files within a package but can't download individual files in the package.


#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.

#16519 - 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 to ensure the ports can be used.

#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.

#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.

#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.

#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.

#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.

#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.

#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.

#25002 - Bad display on IE 9 for overlay of Connect plugin of 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.

#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.

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

#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.


IBM Aspera Enterprise/Connect Server: A licensed version of 3.3+.

Linux 64-bit: RHEL/CentOS 6.0+ & 7.0+, SLES 11.0+

Windows 64-bit: XP, 2003, 2008

Browsers: Internet Explorer 8+, Firefox 27+, Safari 6+, Firefox 27+, Google Chrome 32+


Linux 64-bit: aspera-faspex-
md5: a0a5f44caf008c0e08a884457e2cc3e1
sha1: beca8f70f97fbef82a64964ff2b41b33676e326e
Windows 64-bit: AsperaFaspexSetup-
md5: 2256839fb0174a7476f843089e237c3b
sha1: 0470d2648bd51730279783be05815026f2cfe10a


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.