faspex™ 3.0.3 Release Notes
Created: September 7, 2012
- Numerous GUI updates and bug fixes.
- Self-registration and related security settings.
- Enforce private address book for faspex users.
- Invite outside senders to send packages to internal users.
- Save metadata to a file for normal packages.
- Allow Administrators to specify customized password strength via faspex.yml.
- Apply faspex license via the UI.
- Configure faspex to work with remote transfer server node and web server node (via Aspera Node API).
- Public URL for dropboxes and users.
- asctl command for copying your SSL files into Aspera's default location (under default names).
- asctl apache:install_ssl_cert cert_file key_file [chain_file]
- After upgrading Faspex and Common, use this command to copy your original SSL certificate, key and optional chain file to /opt/aspera/common/apache/conf and give them Aspera-standard names. The httpd-ssl.conf file is also re-rendered and permissions/ownership is set for the cert files.
- Enterprise Server v3.0+
- Aspera Common Components v1.1.11
- IMPORTANT: If you are running your Aspera Enterprise Server on Isilon OneFS, do not upgrade to Faspex v3.0+! You should not upgrade until Aspera Enterprise Server 3.x is available on your Isilon OneFS platform.
Multi-server functionality is not supported in this version.
(#11027) During an upgrade on Windows 2008 32-bit, Apache may report an error when attempting to restart (“Apache HTTPD Server (Aspera): The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.”).
WORKAROUND: Install the Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) package. The download link is at http://www.microsoft.com/en-us/download/details.aspx?id=5582
- (#12709) Users upgrading from faspex v2.0.10 may have to regenerate their “Welcome Email” template if text from the Additional Comments field is not included email. To regenerate, log into faspex and go to Server > Notifications > Welcome Email > Customize Using Template. Click the "Load Defaults" button, followed by "Generate E-mail and Save."
- (#13835) faspex cannot connect to an AWS mail server using TLS; however, SSL connects successfully. Relevant to the settings under Server > Notifications > E-mail Configuration.
- (#14423) Post-processing scripts need to be modified as specified below, since the package’s full path is no longer supplied to the scripts.
- If the transfer server is on the same machine (i.e. node) as faspex, then existing post-processing script(s) must be modified to prepend the faspexuser’s docroot to the package path. After prepending the docroot, check for an extra "/" in the path (e.g. the input "/home/faspex/faspex_packages/$faspex_pkg_directory" will result in the output "/home/faspex/faspex_packages//10d8a2f1-30f4-47ad-a55b-6f8dbba7ff8d/PKG - foo"
- If the transfer server is on a different machine, then existing post-processing script(s) must invoke the Node API, or the remote volume will need to be mounted on the faspex server.
- (#14550) After installation on a Windows machine, the Event Viewer indicates an application error for the Apache Service. This message can be ignored.
- (#15183) In Firefox v12 and older, drag-and-drop stops working when switching from a remote source to the local source on the “New Package” screen.
- (#15401) Metadata can now be exported for normal packages (in previous versions, this was restricted to dropboxes). Note that the saved metadata file is no longer called aspera-dropbox-metadata.xml, but aspera-metadata.xml (even for dropbox packages).
- (#16518) After restoring faspex from a backup (in faspex UI, go to Server > Configuration > Save/Restore), packages will be visible on the server packages screen, but will not be retrievable via faspex. Note has also been added to documentation.
- (#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 pre-3.0.3 and the transfer server is already set up on a different server, asctl will not handle this case. Please contact Aspera Support for assistance.
- (#15977) Relevant ONLY to users who upgraded from faspex v3.0.0 with Enterprise Server v2.8.1 to faspex v3.0.3+ with Enterprise Server v2.8.2+. If you uploaded a remote package to faspex 3.0.0 with the EAR option selected and inputted a passphrase, you can enter any passphrase to decrypt and download the package from the server. This occurs because EAR was not functioning properly in v3.0.0.
- (#16905) The faspex 3.0.3 Windows installer will crash if you attempt to install with the “faspex” user credentials.
- (#16932) faspex 3.0.3 does not handle the tilde (~) character correctly. Packages that contain files with the tilde character at the beginning of the filename cannot be downloaded.
- (#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.
- (#17055) A fresh installation or an upgrade to Faspex 3.0.3 results in errors on CentOS 6.2 32-bit.
- (#17089) After restoring Faspex 3.0.3 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.
- 819f65a6d4e8539cd85895d41ceb86b9 aspera-faspex-22.214.171.124736-0.i386.rpm
- 3f14c57426e2e848a6193cf6eed28172 aspera-faspex-126.96.36.199736-0.x86_64.rpm
- e4bd5695f93a246e6c27f83f8a8c6260 AsperaFaspex-188.8.131.52736-windows-32.msi
- 211d96bb528ddc7730c06831518b8a10 aspera-common-184.108.40.206666-0.i386.rpm
- ed42776aaa674d33c6f6591dbe4edea3 aspera-common-220.127.116.11666-0.x86_64.rpm
- f3b0ece8e022277d6acd4ed40043408ad8ce7570 aspera-faspex-18.104.22.168736-0.i386.rpm
- f85ed99c71bf64979188e674e9a89a854677e1cc aspera-faspex-22.214.171.124736-0.x86_64.rpm
- f0f382064aa9fc958b1924e0a536c1d9112bb195 AsperaFaspex-126.96.36.199736-windows-32.msi
- b8dd0727dd34e543dea212f3a4ccd46bedd64e3d aspera-common-188.8.131.52666-0.i386.rpm
- 1582a611add7a27470694ad8ab9d60705409380a aspera-common-184.108.40.206666-0.x86_64.rpm