older versions of firefox for aspera connect

performs various desktop UI integrations (icons etc.)īefore going through the troubleshooting steps below make sure the Connect installation meets the requirements specified in the user documentation and release notes particularly with regard to the supported versions of operating systems browsers and (if Linux) OpenSSL.installs a protocol handler forthe faspprotocol.installs the Connect application on a local hard disk.

The Connect installation process performs the following tasks: If the box says No Plugin, then your connection to the web interface is serviced by the Connect application itself (2),and you are reading the correct KB article.For table items that say ActiveX or NPAPI, see the KB article Connect (Plugin Version) Does Not Start or Respond. (2) A newer technology that does not use plugins: With this approach, the web interface is serviced by the Connect application directly.īefore proceeding, find your platform, browser, and Connect version in the table below. (1) The traditional browser plugin technology, using ActiveX (Windows IE only), or the NPAPI protocol: With this approach, the web interface is serviced by a plugin. Starting with version 3.6.5,the web interface for the Connect application is serviced by either of the following two technologies, depending on the OS, the browser, and the version of Connect: This article explores ways to troubleshoot such issues.

Sometimes, depending on the environment, Aspera Connect may not launch or respond.

Older versions of firefox for aspera connect