To use HTTP or HTTPS Fallback for a transfer server on a separate (remote)
machine, you must configure the transfer server's firewall settings as well as
IBM Aspera Faspex's security settings. For more information, see
Configuring HTTP and HTTPS Fallback.
Note: You must
have IBM Aspera Connect Server installed to use the HTTP or HTTPS Fallback
features.
-
Configure the transfer server and its firewall ports to enable HTTP fallback. You can configure your transfer server in one of two ways:
- Enable and set HTTP/HTTPS to defaults (8080 + 8443) and keep firewall
ports open on 8080/8443.
- Enable and set HTTP/HTTPS to defaults (80 + 443) and keep firewall ports
open on 80/443.
-
Match Faspex fallback settings to the
transfer server's fallback settings.
Ensure that the transfer server has HTTP or HTTPS fallback enabled within the
Web GUI
Faspex has
Server >
Configuration > Transfer Options > Enable HTTP Fallback and
Server > Configuration > Security > Encrypt Transfers
(for HTTPS fallback) turned on.
Note: For security, Aspera highly recommends
using HTTPS fallback over HTTP fallback. If HTTPS fallback is enabled on the
transfer server, then encrypted transfers must be enabled in Faspex.
HTTP or HTTPS fallback should now be enabled for Faspex using a remote transfer server. If Faspex returns a "Package creation failed" error, it may
mean that the Faspex settings don't match the
settings on your transfer server.