If you are having trouble with the configuration of Aspera Cargo, please go through “EURO 2020 Hive Remote Aspera Cargo configuration” document you have received.
!Important! In Windows you must escape the backward slashes with an extra \.
A UNC path like \\server\share will have to be \\\\server\\share
and a letter mount like M:\path\to\folder will have to be M:\\path\\to\\folder
Frequently "error" messages when installing Cargo:
- Error: private_key file does not exist for account EURO2020 Cargo
Solution: There is either problem with the path in the config file or the file is stored in the wrong place or it has the wrong permissions. Please check the “private_key” config path. Remember to use an extra backward slash \ in the path, if cargo is running on Windows.
Error: Configuration file contains invalid JSON
Solution: Check your config file, you can validate the JSON by pasting into this page: https://jsonlint.com/ - choose “Validate JSON”.
Error: If the logs contains ERR [ascp] Failed to connect to firstname.lastname@example.org, ERR Failed to open a TCP connection for SSH, or ERR [ascp] TCP connect failed, err=111, then there is a firewall issue.
Solution: Check firewall rules: https://nepmediaservices.ibmaspera.com/help/admin/basic-2/system_requirements_and_browser_support
These IPs and ports have to be whitelisted in the customer's firewall.
Allow traffic on TCP/443
Allow traffic on UDP/33001 and TCP/33001
Provide ingress access for the following AoC service IP addresses:
18.104.22.168/31 22.214.171.124/31 126.96.36.199/26 188.8.131.52/31 184.108.40.206/31 220.127.116.11/26 18.104.22.168/31 22.214.171.124/31 126.96.36.199/26 188.8.131.52/29 184.108.40.206/29
Provide ingress access to your AoC node IP addresses:
220.127.116.11 18.104.22.168/27 22.214.171.124/27 126.96.36.199/27 188.8.131.52/27
Error: If the logs contain lines with permission denied, then there is an issue with the permissions on the download path for the user running Cargo.
Does the user Cargo is running with, have read and write access to the download path?
Try to create and delete a file with the same user that is running Cargo.
If the user is not able to create or delete the file, change the permissions so that the user running Cargo has the correct access or change to another user that has the correct access.
Example Config JSON:
"name": "EURO2020 Cargo",
"private_key": " C:\\Aspera\\Cargo\\private_key_path",
"name": "EURO2020 Cargo Packages",