Need advice to migrate from Aspera CLI version 3.9.6.1467.159c5b1 to Aspera CLI 4.20.0 to connect to

[cph1c06]

When attempting to use the IBM Aspera CLI (version 3.9.6.1467.159c5b1) to send a file via Aspera Faspex, a JSON parse error occurs. The command was executed to send a file to a recipient "content upload" with a title "Test Title" to the server, but the POST request to https://$IP:$PORT/aspera/faspex/send failed with a JSON parse error at character

aspera --version
IBM Aspera CLI version 3.9.6.1467.159c5b1

aspera faspex send -H "$IP" --file $FILENAME --title "Test Title" --recipient "content upload" --username $USERNAME --password $PASSWORD -i
Building JSON... done
Serializing JSON... done
POSTing to https://$IP:$PORT/aspera/faspex/send... JSON parse error at character 0: Invalid value.

We had concluded this CLI version is not able to send packages to Faspex 5 as it is not supported with Faspex 5.

asperaconnect faspex send -f $FILENAME -n "Viu uploaded: TEST" -t "Viu uploaded: TEST" -r "VIUHK content upload" -u$USERNAME -H$IP -p$PASSWORD -i
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.

May I know how to fastly migrate from aspera cli 3.9 to 4.20.0? Many thanks!

[laurent-martin]

Hi,

Right, the Aspera CLI 3.x is not more supported and is replaced with CLI v4.x, ascli in this repo.

Installation procedure is included in the manual (install ruby, then gem, then ascp). There are several ways to install.

If you are using a recent Linux, you might try single executables from: https://eudemo.asperademo.com/download/aspera-cli/

ascli comes with a wizard to help with the configuration, or you can do the manual configuration as well.

For example:

ascli config wizard https://faspex5.example.com/path faspex5

The manual for CLI on Faspex5 is here: https://github.com/IBM/aspera-cli?tab=readme-ov-file#plugin-faspex5-ibm-aspera-faspex-v5

Upon wizard use, or manual configuration, a config file is created, making it easier to execute individual commands, nevertheless, the config file is not mandatory and all options can also be placed on the command line.

Then to send a package:

ascli faspex5 packages send @json:'{"title":"some title","recipients":["user@example.com"]}' mybygfile1

have a 🍺