Troubleshooting Aspera

Review these FAQs to help in troubleshooting some known issues with Aspera and NetStorage.

Question Answer
What information is needed to investigate (and if necessary, escalate) an Aspera issue? We need the following information:
  • The Aspera Client log

  • The time of failure (and timezone)

  • The name(s) of file(s) which failed

You can work with your Account Representative to gather this information.

I’m getting transfer rates of only 40mbps. Can I increase this? The Aspera Client has a 45 mbps threshold configured by default. It can be increased via Control Center (Tools > Preferences > Default Target Rate).

Keep in mind that the Aspera Client will use all available bandwidth (up to the configured limit) on your local network, so set a limit that will work well with other network traffic.

I am specifying an SSH key via ASCP, and it will not authenticate properly to Aspera, but this same key works via SCP. What am I doing wrong? ASCP always expects a full path name when the “-i” tag is specified to denote a key. For example, the following shows how to properly call out the key via ASCP:

ascp -i <path>/.ssh/keyfile.key

The “ <path> ” value represents the full path to your home directory (For example, “ /home/$USERNAME ”, by default).

However, with SCP, you could simply specify the following, and the key would be resolved, but it does not work via ASCP:

ascp -i .ssh/keyfile.key

This is a known limitation with Aspera, and requests have been made to correct it in a future release.