Mandatory Aspera Connect 3.6 upgrade

Google announced late last year NPAPI plug-in support would be disabled by default in Chrome starting in April 2015, which enabled your Chrome browser to communicate with your Aspera Connect transfer client.  Some of you might have experienced this issue and have been instructed by our Customer team to re-enable NPAPI to continue use Aspera Connect with Ci.


In May 2015, Aspera released a new 3.6 version of Aspera Connect that no longer relies on NPAPI.  Google has announced support for NPAPI will be eliminated by September 2015 to improve Chrome’s security and stability (starting with Google Chrome 42.0.2311.90)


We decided to adopt Aspera Connect 3.6 to get our users over the line early and enable us to provide the best experience and support are based on most current technologies.  If you are an Aspera Connect user, you will soon be prompted upon login to upgrade if you would like to continue to use Aspera with Ci.  Unfortunately, this will be a mandatory upgrade requiring you to spend 5-10 minutes to go through the download & installation process.  To download, the current version of Aspera Connect, please go to this link:


To learn more about Google’s decision to eliminate support for NPAPI, go here:


Other references around this Google NPAPI access change:

Have more questions? Submit a request


Article is closed for comments.