Configuring HTTP and HTTPS Fallback

HTTP fallback serves as a secondary transfer method when the Internet connectivity required for Aspera FASP transfers (UDP port 33001, by default) is unavailable. When HTTP fallback is enabled and UDP connectivity is lost or cannot be established, the transfer will continue over the HTTP protocol.

The instructions below describe how to enable and configure HTTP/HTTPS fallback. These instructions assume that you have already configured your Connect Server's Web UI. For additional information on configuring different modes and testing, see the Aspera KB Article "HTTP fallback configuration, testing and troubleshooting."

  1. Configure HTTP/HTTPS fallback settings.
    You can configure HTTP/HTTPS Fallback from either the GUI or by editing aspera.conf.

    Configuring HTTP/HTTPS fallback from the GUI:

    Launch the transfer server and go to Configuration > Global > HTTP Fallback.

    Configuring HTTP/HTTPS fallback by editing aspera.conf:

    Run the following commands:

    • To view the current HTTP settings in aspera.conf:
      $ asuserdata -b -t

    To manually inspectaspera.conf, open it from the following directory:

    C:\Program Files (x86)\Aspera\\etc\aspera.conf

  2. After enabling HTTP fallback and setting a token encryption key, restart the Aspera Central, Aspera NodeD, and Aspera HTTPD services.

    You can restart the Aspera Central from the Computer Management window. Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera Central, and click Restart.

    Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera NodeD, and click Restart.

    Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera HTTPD, and click Restart.