Troubleshooting File Storage Errors

If file storage is not properly configured for Faspex, Faspex displays the following error at the top of every page: "WARNING! Transfer server errors detected, transfers may not operate correctly"

You can test the file storage for errors by testing the connection between Faspex and the remote transfer node. Go to Server > File Storage, click the arrow next to the node, and select Edit from the drop-down menu. Select Test Connection. If the connection is successful, Faspex displays: "Connection succeeded!" Otherwise, Faspex displays an error.

See the following list of common errors and their possible solutions:

not pingable: SSL error

Faspex displays this error if you select Verify SSL Certificate but do not have a valid SSL certificate installed. Deselect Verify SSL Certificate or install a valid SSL certificate following the instructions in Working With SSL.

not pingable: Connection refused

Faspex may display this error if the Aspera NodeD service is down. To restart the Aspera NodeD service, on the node, run the following command
# service asperanoded restart
The connection may also be refused if the SSH port (port 22) is closed on the node. To check and open the port, follow the instructions below:
  1. Open the /etc/ssh/sshd_config file in a text edtior.
  2. If Port 22 is commented, uncommented the line. If Port 22 is missing, add the line into the file.
  3. Save the file.
  4. Restart the SSH service:
    service sshd restart

not pingable: Internal error

Node not configured correctly. For example, no valid license?
  1. First, restart the Aspera NodeD service. It is possible that you made changes to aspera.conf or the license file without restarting Aspera NodeD. The service must be restarted for Faspex to recognize the changes. To restart the Aspera NodeD service, on the node, run the following command
    # service asperanoded restart
  2. If the issue is not resolved, make sure the node is fully configured for use with Faspex by reviewing the instructions Configuring a Remote Transfer Node for Faspex.

not infoable: Not authorized

The Node API user credentials you entered do not match a valid Node API user on the transfer node.
  1. Log into your transfer node and run the following command:
    # /opt/aspera/bin/ asnodeadmin.exe -l
  2. If your Node API user is not listed in the output or it is not associated with the faspex system user, use the correct user associated with the faspex system user or create a new Node API user and associate it with the system user. To create a new user, run the following command:
    # /opt/aspera/bin/asnodeadmin -a -u node_username -p node_password -x faspex
    For example:
    # /opt/aspera/bin/asnodeadmin -a -u faspex_node_user -p ********* -x faspex