A user is unable to launch the Aspera Connect plugin on the same system where other users are using Connect at the same time. When visiting an Aspera server site, Connect fails to launch and the user may see a blue banner prompting them to download the latest version of Connect.
This problem affects users on Windows operating systems using non-NPAPI browsers (for example, Chrome). By default Connect allows 10 users on the same system to simultaneously use the plugin. If you are limited to less than 10 Connect users at the same time, follow the solutions below.
If you need more than 10 users to use Connect at the same time on the same system, you will also need to modify your web application (see this Knowledge Base article).
This problem occurs because of a file that retains outdated connection information (the local socket address) from a previous Connect session. When a user tries to use Connect, the plugin uses the outdated connection which may currently be in use by another user, so Connect is unable to launch.
A future release of Connect will remedy this issue. In the meantime, deleting this file forces Connect to look for an available port rather than using the same as the previous session, and allows 10 users on Connect concurrently as expected.
The file to delete is
http.uri which can be found at the following, where username is the name of a Windows user account: