Configuring HTTP and HTTPS Fallback

HTTP Fallback serves as a secondary transfer method when the Internet connectivity required for Aspera accelerated transfers is unavailable. UDP is set to port 33001, by default. When HTTP Fallback is enabled and UDP connectivity is lost or cannot be established, the transfer continues over the HTTP protocol.

Note: This feature requires IBM Aspera Enterprise Server with a Connect Server-enabled license.
  1. Edit the aspera.conf file located at the following location:
    OS Version File Location
    32-bit Windows C:\Program Files\Aspera\Enterprise Server\etc\aspera.conf
    64-bit Windows C:\Program Files (x86)\Aspera\Enterprise Server\etc\aspera.conf
  2. Add the following section to the configuration file:
    <?xml version='1.0' encoding='UTF-8'?>
    <CONF version="2">
    ...
        <http_server>
            <http_port>8080</http_port>
            <enable_http>1</enable_http>
            <https_port>8443</https_port>
            <enable_https>1</enable_https>
        </http_server>
    ...
    </CONF>
  3. After modifying aspera.conf, restart the Aspera Central, Aspera NodeD, and Aspera HTTPD services:
    Go to Control Panel > Administrative Tools > Services. For each service, right-click the service and select Restart from the menu.
  4. Run the following command to validate your updated configuration file:

    > C:\{Program Files or Program Files (x86)}\Aspera\Enterprise Server\bin\asuserdata -v
For more details on how to perform these tasks, see the "Configuring HTTP and HTTPS Fallback" topic in your Connect Server Admin Guide.
In the event that you need to modify your HTTP Fallback port number, configure the following section in your aspera.conf file by replacing http_port and https_port with your new port number:
<http_server>
    <http_port>1234</http_port>
    <https_port>1234</https_port>
    <enable_http>true</enable_http>
    <enable_https>true</enable_https>
</http_server>
Warning: If IBM Aspera Shares is set to use Encryption-at-Rest, downloading unencrypted content through HTTP Fallback will fail with the following errors:
  • Downloading unencrypted files or folders will fail with the "Insufficient permissions" error.
  • Downloading a mix of encrypted and unencrypted files or folders together will fail with the "Connection lost" error.
  • Downloading a mix of folders, some folders with only encrypted files and other folders with only unencrypted files, will fail with the "Server refused request" error.
  • Downloading encrypted files or folders with the wrong passphrase entered will fail with the "File decryption error, bad passphrase" error.