System Requirements
Overall Requirements
| Operating System |
Note: Aspera will be dropping support for Windows XP and
Windows Server 2003 in six months.
Important: The name of your Windows machine
cannot be "FASPEX", otherwise installation will fail. The Faspex installer will attempt to create
the user "faspex" and if this is the same as the machine name the
account creation will fail.
|
| Browsers |
|
| Aspera Product Version Requirements |
|
| Memory |
|
| Applications |
|
Firewall Settings
An Aspera server runs one SSH server on a configurable TCP port (33001 by default).
Your firewall should be configured as follows:
- To ensure that your server is secure, Aspera strongly recommends allowing inbound connections for SSH on TCP/33001 (or on another non-default, configurable TCP port), and disallowing inbound connections on TCP/22. If you have a legacy customer base utilizing TCP/22, then you can allow inbound connections on both ports.
- Allow inbound connections for FASP transfers, which use UDP/33001 by default, although the server may also choose to run FASP transfers on another port.
- If you have a local firewall on your server (such as Windows Firewall), verify that it is not blocking your SSH and FASP transfer ports (TCP/UDP 33001).
- For the Faspex application, allow inbound connections for HTTP and/or HTTPS Web access (TCP/80, TCP/443).
The firewall on the server side must allow the open TCP port to reach the Aspera server. No servers listen on UDP ports. When a transfer is initiated by an Aspera client, the client opens an SSH session to the SSH server on the designated TCP port and negotiates the UDP port for the data transfer.
For Aspera servers that have multiple concurrent clients, the Windows operating system does not allow the Aspera FASP protocol to reuse the same UDP port for multiple connections. Thus, if you have multiple concurrent clients and your Aspera server runs on Windows, then you must allow inbound connections on a range of UDP ports, where the range of ports is equal to the maximum number of concurrent FASP transfers expected. These UDP ports should be opened incrementally from the base port, which is UDP/33001, by default. For example, to allow 10 concurrent FASP transfers, allow inbound traffic from UDP/33001 to UDP/33010.
Faspex Domain name
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, admin@faspex.example.com) 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.
Drag-and-Drop Support
Faspex supports the dragging and dropping of files and folders for transfer, but this support varies by platform and browser. See the table below for details on how this release of Faspex supports drag-and-drop in your environment:
| Browser | Windows Client | Mac OS X Client | Linux Client |
|---|---|---|---|
| Firefox | Files and folders | Files and folders | Drag-and-drop not supported |
| Chrome | Files and folders | Files and folders | Drag-and-drop not supported |
| IE 8 and 9* | Files and folders | — | — |
| IE 10 and 11* | Files | — | — |
| Edge* | Drag-and-drop not supported | — | — |
| Safari | — | Files and folders | — |
* Internet Explorer is limited in support for drag-and-drop because of how it records drop events. Edge does not support drag-and-drop from the system into the browser. For further information, see