Configuring HTTP and HTTPS Fallback

HTTP fallback serves as a secondary transfer method when the Internet connectivity required for Aspera accelerated 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 walk through the process of setting up HTTP/HTTPS fallback. For additional information on configuring different modes and testing, see the Aspera KB Article "HTTP fallback configuration, testing and troubleshooting."

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

From the GUI

To edit your settings from the GUI, launch the transfer server and go to Configuration > Global (tab in left pane) > HTTP Fallback (tab in right pane).
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.
Run the following command (from Enterprise Server's bin directory) to validate your updated configuration file: