Troubleshooting File Storage Errors
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 Installing a Signed SSL Certificate Provided by Authorities.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:
- Open the /etc/ssh/sshd_config file in a text edtior.
- If Port 22 is commented, uncommented the line. If Port 22 is missing, add the line into the file.
- Save the file.
- Restart the SSH service:
service sshd restart
not pingable: Internal error
Node not configured correctly. For example, no valid license?- 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
- If the issue is not resolved, make sure the node is fully configured for use with Faspex by reviewing the node setup instructions. Fore more information, see Configuring Transfer Servers for Use with Faspex.
not infoable: Not authorized
The Node API user credentials you entered do not match a valid Node API user on the transfer node.- Log into your transfer node and run the following
command:
# /opt/aspera/bin/
asnodeadmin.exe -l - 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:
For example:# /opt/aspera/bin/
asnodeadmin -a -u node_username -p node_password -x faspex# /opt/aspera/bin/
asnodeadmin -a -u faspex_node_user -p ********* -x faspex