Users Cannot Transfer

The change in security policies on macOS as of 10.11 (El Capitan) can interfere with a transfer user's ability to transfer.

Cannot run FASP transfers from command line or GUI

If your transfer user cannot transfer from the command line or GUI:

  1. Ensure that the file /Users/username/.ssh/environment exists for the user and contains the following text:
    PATH=/bin:/usr/bin:/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/opt/pkgconfig/bin:/Library/Aspera/bin:/Library/Aspera/sbin
  2. If the user was configured to use aspshell, ensure that the path is correct:
    1. Go to System Preferences > Users & Groups.
    2. Click the lock icon and enter admin credentials.
    3. Right-click the username and click Advanced Options.
    4. Change the login shell to /Library/Aspera/bin/aspshell if it is not already.
    5. Click OK to save your changes.

Node user cannot transfer

The Aspera RSA key does not contain the correct path to aspshell, so if the transfer user who is associated with the node user is not assigned to aspshell, then the node user cannot transfer.

Workaround: Either assign the transfer user to aspshell (for instructions, see Setting Up Users or Setting Up Transfer Users) or edit /Library/Users/username/.ssh/authorized_keys, changing the first line:
command="/bin/aspshell -t",...
to
command="/Library/Aspera/bin/aspshell -t",...

Aspera recommends making the same change to /Library/Aspera/var/aspera_tokenauth_id_rsa.pub so that when it is added to any other user's authorized_keys file, the path is correct.