Common Errors in Faspex

Errors Displayed in IBM Aspera Connect

When uploading a file to Faspex, Faspex launches Connect to perform the transfer from your machine to the server. If the upload fails, Connect displays an error. See below for common error messages.
Error Code Error Message Issue Solution
Code 44 Error: Failed to open TCP connection for SSH Faspex uses port 33001 to connect to the node. If the node is running a Linux operating system, port 33001 may not be open. If your node is a Linux machine, open the sshd_config file (C:\Program Files (x86)\Aspera\Enterprise Server\etc\sshd_config) in text editor and add the lline Port 33001 to the configuration file to enable access to port 33001.

If you change settings, you must restart the OpenSSH service. You can restart these services from the Windows Computer Management window, accessible from Manage > Services and Applications > Services. Right-click OpenSSH Service and select Restart from the menu.

Code 19 Error: Authentication failed Faspex uses Connect key to authenticate an SSH connection with Connect. An authentication failure may mean a missing key. Copy the contents of the key (C:\Program Files (x86)\Aspera\Enterprise Server\var\ into the authorized_keys file (C:\Documents and Settings\faspex\.ssh\authorized_keys).
Note: Make sure the authorized_keys file has no file extension. Some text editors add a .txt extension to the filename automatically. Be sure to remove the extension if it was added to the filename.

Package Creation Error on the New Package Page

When trying to create a new package (New Package or New Package > Normal Package), Faspex displays the Package creation failed error message.

Faspex may display this error message if HTTP Fallback is configured incorrectly. The fallback settings for the transfer server product (IBM Aspera Enterprise Server or IBM Aspera Connect Server) must match the Faspex fallback settings. For more information, see Configuring HTTP and HTTPS Fallback.