Workaround for use of Aspera Connect with Google Chrome version 42.0.2311.90

NOTE: Chrome has completely removed NPAPI support since September 1st 2015. At this point the workaround in this article is no longer available. If you have not done so you must to update to the latest version of Connect (3.6.0 or later) in order to continue using Connect in Chrome. For more information, please see this article: Using Aspera Connect after the Google Chrome 45 release

 

Description

Google Chrome version 42.0.2311.90 (64-bit) has the NPAPI plugin support disabled by default. NPAPI is required on Chrome by Aspera Connect versions earlier than 3.6.0 when uploading and downloading from Aspera enabled web servers.

The feature is disabled by default in Chrome 42.0.2311.90 and higher but can be manually re-enabled.

 The applications affected are:

  • Aspera Connect (all versions)
  • Faspex (all versions)
  • Shares(all versions)
  • Connect Server (all versions)

 

Resolution

Aspera has already developed and released a version of Aspera Connect (3.6.0) that no longer uses NPAPI. Minor updates have been made to newer versions of Faspex (3.9.2 and later), Shares (1.9.2 and later) and Connect Server (3.5.5 and later) to accommodate the new Aspera Connect, so ensure your servers are up to date. The latest version of Connect is available at Aspera's downloads page.

 

The temporary workaround to use Connect (versions earlier than 3.6.0) in Chrome is the following:
1. In your address bar, go to:
chrome://flags/#enable-npapi

2015-04-14_1837.png

2. Click the Enable link under Enable NPAPI.

3. Quit Chrome entirely and restart.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk