|Configuring the Server|
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."
Additionally, the transfer server fallback settings must match the Faspex fallback settings. If the settings don't match, Faspex returns a "Package creation failed" error. Ensure that transfer server has HTTP/HTTPS fallback enabled.
To confirm your HTTP Fallback port number, run the following asctl command:
$ asctl faspex:http_fallback_portIf you need to modify the Faspex HTTP port, add the port_number to the command:
$ asctl faspex:http_fallback_port port_number
You can configure HTTP/HTTPS Fallback from either the transfer server 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).
Review the following settings:
To change your HTTP fallback settings from aspera.conf, go to the following directory:
Confirm the HTTP fallback settings in aspera.conf as shown in the example below. enable_http should be set to true, while the value shown for http_port should match what was displayed when you ran the command asctl faspex:http_fallback_port (default: 8080).
<CONF version="2"> ... <http_server> ... <enable_http>true</enable_http> <!-- Enable HTTP --> ... <http_port>8080</http_port> <!-- HTTP port --> ... </http_server> </CONF>
# service asperacentral restart # service asperanoded restart # /etc/init.d/asperahttpd restart
$ /opt/aspera/bin/asuserdata -v