Aspera recommends creating a domain name for Faspex. If Faspex is configured to identify itself by IP address (rather than by domain name), then the URLs in your notification emails contain an IP address (for example, "https://10.0.0.1/aspera/faspex"). Some Web-based email services (such as Yahoo or Ymail, and Hotmail) have been known to automatically flag emails containing IP address links as "Spam," and move them to your Junk/Spam folder. If you do not have a domain name immediately available, then you can first configure Faspex with an IP address and then change it to use a domain name later.
If you know that you will not be setting up a domain name, make sure that users add your Faspex "From" email address (for example, firstname.lastname@example.org) to their address book or contact list. Doing so typically "white-lists" the address so that emails from Faspex are not automatically flagged and routed the Junk/Spam folder.
Download the latest version of IBM Aspera Enterprise Server,Common Components and IBM Aspera Faspex installers from the following locations:
You are required to enter your organization's Aspera login credentials to gain access. If you need help determining your organization's access credentials, contact Technical Support.
For instructions on installing your software and license, follow the steps in the IBM Aspera Enterprise Server or IBM Aspera Connect Server Admin Guide.
The transfer server can be set up in either of the following configurations:
# service asperacentral restart # service asperanoded restart
Add the line Port 33001 to the configuration file to enable access to port 33001. If you are also using port 22 for shell access to the server you also need to add or uncomment the line Port 22 in the config file.
Restart the SSH server to apply your new settings:
# service sshd restart