Learn how to troubleshoot the error messages that you can get in the application.
The following list has the common issues that you can encounter:
Request rejected by proxy (Error 11)
| Explanation |
The specified transfer proxy denied the request. |
| Action |
Confirm that the transfer proxy is configured correctly in Settings > Proxies. If the issue persists, contact your system admin to check that the transfer proxy is configured correctly. |
Failed to open TCP connection for SSH (Error 44)
| Explanation |
By default, Aspera for desktop establishes an SSH connection to the transfer server before starting the transfer. If your computer is behind a restrictive firewall, it is possible that this connection is being blocked which might result in the transfer failure. |
| Action |
Unless otherwise specified, Aspera for desktop uses TCP port 33001 for this SSH connection. Confirm with your IT department that your firewall allows outbound connections for file transfers on TCP port 33001. |
Client unable to connect to server (check UDP port and firewall) (Error 15)
| Explanation |
When the transfer is started, Aspera for desktop is required to connect to the server over UDP. If your computer is behind a restrictive firewall, it is possible that UDP connectivity is blocked which might result in the transfer failure. |
| Action |
Unless otherwise specified, Aspera for desktop uses UDP port 33001 for file transfers. Confirm with your IT department that your firewall allows traffic on UDP port 33001. |
The connection to the server was lost (Error 16)
| Explanation |
The system either couldn't establish a connection to the server or lost it.
Common error messages:
- Session shutdown failed, failure while draining incoming flow
- Client quit unexpectedly, UDP recv got "Connection refused"
|
| Action |
Check whether your network is working and retry the transfer. |