How to support more than 10 concurrent Connect transfers or users on a single client machine


On non-NPAPI, non-ActiveX browsers (Chrome, Edge), the Aspera Connect browser plugin allows a maximum of 10 users on the same client computer to use Connect at the same time. This is a default setting, and if you need to support more than 10 concurrent users or transfers per client you can change this limit to one of your choosing.

Changing this limit requires you to make changes to the web application your users are accessing and using Connect with. The change will be made to a javascript file that is served to and run in the client's browser.

In addition, your web application server must be locally hosting Connect plugins and installers, rather than having them served by Aspera. (For more information on how to locally host Connect, see the following Knowledge Base articles for Faspex, Shares and Connect Server).


You can change the concurrent user limit by editing the file asperaweb-4.js.

The location of this file depends on your web application and where you placed the Connect local hosting files, which come with the Connect SDK. If you followed the Knowledge Base instructions for locally hosting Connect for Faspex, Shares or Connect Server, the file should be in one of the following locations:


  • Linux: /opt/aspera/faspex/connect/v4/asperaweb-4.js
  • Windows: C:\Program Files (x86)\Aspera\Faspex\connect\v4\asperaweb-4.js


  • Linux: /opt/aspera/shares/u/connect-sdk/v4/asperaweb-4.js
  • Windows: C:\Shares\connect-sdk\v4\asperaweb-4.js

Connect Server

  • Linux: /opt/aspera/var/webtools/connect/v4/asperaweb-4.js
  • Windows: C:\Program Files (x86)\Aspera\Enterprise Server\var\www\connect\v4\asperaweb-4.js
  • Mac OS X: /Library/Aspera/var/webtools/connect/v4/asperaweb-4.js

1. Open this file in a text editor. Around line 535, locate the following two lines:

//Controls how many ports we want to search from the DEFAULT_PORT     

Change the value for MAX_PORT_SEARCH to the number of concurrent users on a single client computer you need to support. Save the file.

2. Aspera's web apps use and reference the minimized version of asperaweb-4.js, and if you have a custom application it may be using the minimized version as well. If that is the case there is one more step to perform.

Minimizing javascript files is generally good practice for faster loading, but it is not required.

If you would like to continue using a minimized file, minimize the edited asperaweb-4.js file, rename it asperaweb-4.min.js and replace the original, which is located in the same v4 directory where asperaweb-4.js is. You can use a tool such as Uglify-JS to minimize your file.

If you would prefer not to minimize asperaweb-4.js, you can simply make a copy of it and rename it asperaweb-4.min.js in the same directory.


Powered by Zendesk