Troubleshoot the problem that your clients cannot connect to your IBM Aspera Connect Server.
The following diagram shows the troubleshooting procedure if clients can't establish a FASP transfer connection to your Connect Server. Follow the instructions to identify and resolve problems:
> telnet 10.0.1.1 33001
On Connect Server, test both the SSH connection ports and the web server ports (HTTP and HTTPS).
If the client cannot establish connections to your Connect Server, verify the port number and the firewall configuration on the Connect Server machine.
> ssh email@example.com -p 33001
If the SSH service runs normally, the client should see a message prompting to continue the connection or for a password. However, if you see a "Connection Refused" message, which indicates that the SSH service isn't running, review your SSH service status. Ignore the "permission denied" message after entering the password, which is discussed in next steps.
If your Connect Server responds to the client's SSH login attempt, try prompting for login credentials, the user account may not be properly configured for FASP connections. Make sure that the login information is correct, and refer to Setting Up Users to review the user account's configuration. Web UI requires login users to have docroot configured.
If you still encounter connection problems after going through these steps, contact Technical Support.