Testing the Web UI

Follow the steps below to test your Aspera Connect client transfers through the Web UI.

Note: The instructions require steps to be taken on both the Connect Server system and a client computer. Make sure you are performing the steps on the specified machine.
  1. Connect Server: Configure a user for FASP file transfer (GUI).
    Note: To configure the user from the command line, see the next step.

    Prepare a system user and add the user into your Connect Server, with a docroot specified. Run asperascp (as a root user) to launch the application, and click Configuration.

    Click Configuration.

    In the Server Configuration dialog, select the Users tab and click Add user. Enter the system user's name (asp1).

    Add the test user.

    Select the user's Docroot tab; check Absolute Path; and enter or select an existing path as the user's docroot (for example, /sandbox/asp1). Make sure that all other options have the value true. Click OK or Apply when finished.

    Set up the docroot.
  2. Connect Server: Configure default values for FASP file transfer (Terminal)
    Note: Skip this step if you have configured the user from the GUI.

    Set default values to authorize transfers in and out, set the encryption key, and set the default docroot by running the following commands:

    $ asconfigurator -x "set_node_data;authorization_transfer_in_value,allow"
    $ asconfigurator -x "set_node_data;authorization_transfer_out_value,allow"
    $ asconfigurator -x "set_node_data;token_encryption_key,token_key"
    $ asconfigurator -x "set_node_data;absolute,docroot"

    These commands create the following lines in aspera.conf. In the example, the encryption key is secRet (rather than the random string of at least 20 characters as recommended by Aspera) and the docroot is /sandbox/$(name). By using the substitutable string $(name) in the docroot, the application automatically replaces it with the login user name:

    <CONF version="2">

    To add the settings to aspera.conf manually, open it from the following directory:


  3. Connect Server: Configure Apache authentication for the system user.
    In addition to SSH authentication, Connect Server uses Apache's authentication to authorize Web UI access. To set up a system user (asp1 in this example) for Apache authentication, run the htpasswd command below.
    Note: On the first run of htpasswd, you must use the -c option to create the file for credential storage, webpasswd. Do not use the -c option otherwise.
    $ htpasswd [-c ]/opt/aspera/etc/webpasswd asp1
    Note: If you have Apache 2.4.4, the above command may not work. You are prompted to enter a password, but you may get authentication errors when attempting to view the site. As a workaround to this bug, run htpasswd with the -b option and enter the password on the command line, as follows:
    $ htpasswd -b /opt/aspera/etc/webpasswd asp1 password
  4. Client: Test the Web UI with the client machine
    Important: Cookies must be enabled in a client's browser.

    Prepare a client computer with the supported OS and browser to test connecting to the Web UI. For a list of supported platforms and browsers, see Requirements. Go to the following address with a client computer's browser:

    HTTP http://server_ip_or_name/aspera/user
    HTTPS https://server_ip_or_name/aspera/user

    Browsing the Web UI from the client machine, you should see the Aspera Connect browser plugin banner with a link to download and install the latest version of Connect:

    Click Download latest version. While waiting for the application to download, the following instructions appear:

    Once the Connect plugin is installed and you've refreshed the page, the Web UI for Connect Server appears:

    In the Web UI, click Upload and select one or more files to upload to Connect Server. When finished, select the uploaded files on the Web UI, and click Download.

    Note: When adding files to the Web UI, do not use the following characters in the filenames:
    / \ " : ' ? > < & * |

    For further information about the Aspera Connect browser plugin, see the Aspera Connect User Guide.

If you are having difficulties establishing FASP transfers using the Web UI, see Clients Can't Establish Connection.