The Aspera Connect client version 3.6 includes a new native Chrome plug-in built using Chrome’s PPAPI (“pepper”) APIs, which brings several advantages.
- First, Connect 3.6 no longer relies on the NPAPI and thus works with the default configuration of Chrome. As of the release of Chrome 45, Chrome has removed support for NPAPI entirely.
In order for your users to take advantage of Connect 3.6 for Chrome browsers, you will need to upgrade to Faspex version 3.9.2 or later.
- Product: Faspex
- Version: Upgrade to 3.9.2
- Operating System: Linux, Windows
1. Back up your Faspex database. For detailed instructions see the Faspex documentation.
2. Download the latest Faspex installers and Common Components from the Aspera download site.
3. (Windows Step Only) Make sure you have Windows Installer 4+. You can download it here.
4. Copy your SSL certificate files server.crt and server.key files to a different location. The files are located at the following:
5. Stop all Faspex services.
You can do so by running the following command:
6. Run the Faspex installers.
On Windows, double click the Faspex installer.
On Linux, run the following commands:
rpm -Uvh aspera-common-<version>.rpm
rpm -Uvh aspera-faspex-<version>.rpm
After the installation finishes, asctl will be launched automatically to begin the set up process. If asctl is not launched, you can run the command manually:
6. Back up your new Faspex database. For detailed instructions see the Faspex documentation.
7. Restore the SSL certificate files you copied in step 3 back to their original locations.
8. Restart Apache and Aspera Node Server.
On Windows, go to Control Panel > Administrative Tools > Services. Locate and select Aspera NodeD and click Restart on the lefthand panel.
On Linux, restart both Aspera Node Server and Apache.
You can restart Apache with the following command:
You can restart Aspera Node Server with the following command:
Your upgrade to Faspex 3.9.2 is complete. Faspex now supports Connect 3.6 on Chrome browsers without NPAPI.