Aspera CLI (v4.25.1) - Multiple command failures: initdemo, browse, and download

[gsk-work]

Multiple Aspera CLI commands are failing or not working as expected on version 4.25.1 with IBM Aspera Transfer SDK 1.1.6.

Environment

• OS: Linux
• Ruby Version: 3.2.4 (2024-04-23 revision af471c0e01) [x86_64-linux]
• Aspera CLI Version: 4.25.1
• IBM Aspera Transfer SDK: 1.1.6
• ascp Version: 4.4.6.2033 31ae48a
• AES-NI: Supported

Issues Encountered

"ascli server browse /" - command failing with demoserver preset

• Expected Behavior:
  • Should browse the root directory of the demo server.
• Actual Behavior:
  • Command waiting at following line without any result (please find tail result of debug logs)

    DEBG URI=ssh://demo.asperasoft.com:33001, host=demo.asperasoft.com, port=33001, scheme=ssh
   DEBG SSH keys=[]
   DEBG ssh:aspera@demo.asperasoft.com
   DEBG ssh_options (json)=
   {
     "port": 33001,
     "password": "",
     "logger": "#<Logger:0x000071547bad89f0>",
     "verbose": "warn",
     "use_agent": false
   }
   DEBG execute_single:ls:["/"]
   DEBG cmd=ascmd
  

ascli shares files download - 401 Unauthorized Error

ascli shares files download \
  --url=https://<ASPERA_SERVER> \
  --username=<USERNAME> \
  --password=<PASSWORD> \
  /config.json \
  --insecure=yes

• Expected Behavior:
  • File should download successfully with valid credentials.
• Actual Behavior:
  • Authentication fails with 401 Unauthorized error.
• Error Output:
  ERROR: Rest: <ASPERA_SERVER> 401 Unauthorized

Important Note:

I was able to login to Aspera Shares UI with the above credentials and successfully download files through the web interface. This confirms that:

• The credentials are valid and working
• The server is accessible and functioning properly
• The issue appears to be specific to the CLI authentication mechanism

[laurent-martin]

1. HSTS
   I have tested as follows:

$ ascli conf init
Done
Saving config file.
$ ascli conf pre over
╭────────────┬───────────┬─────────────────────────────────╮
│ preset     │ parameter │ value                           │
╞════════════╪═══════════╪═════════════════════════════════╡
│ config     │ version   │ 4.25.1                          │
│ demoserver │ url       │ ssh://demo.asperasoft.com:33001 │
│ demoserver │ username  │ aspera                          │
│ demoserver │ password  │ 🔑                              │
│ default    │ server    │ demoserver                      │
╰────────────┴───────────┴─────────────────────────────────╯
$ ascli server br /
╭────────────┬────────┬────────┬───────┬───────────────────────────┬───────────────────────╮
│ zmode      │ zuid   │ zgid   │ size  │ mtime                     │ name                  │
╞════════════╪════════╪════════╪═══════╪═══════════════════════════╪═══════════════════════╡
│ drwxr-xr-x │ aspera │ aspera │ 57344 │ 2026-01-27 16:57:10 +0000 │ Upload                │
│ dr-xr-xr-x │ aspera │ aspera │ 4096  │ 2022-10-27 15:08:16 +0100 │ aspera-test-dir-large │
│ dr-xr-xr-x │ aspera │ aspera │ 4096  │ 2022-10-27 15:08:17 +0100 │ aspera-test-dir-small │
│ dr-xr-xr-x │ aspera │ aspera │ 4096  │ 2022-10-27 15:08:17 +0100 │ aspera-test-dir-tiny  │
╰────────────┴────────┴────────┴───────┴───────────────────────────┴───────────────────────╯

As you can see this works with version 4.25.1, so there must be something else.
In addition, those commands are parts of tests before release.

If it is waiting, it means that probably the port 33001 of the server is not accessible, try the following:

telnet demo.asperasoft.com 33001

or

nc demo.asperasoft.com 33001

In case of success, both shall display:

SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.13

If not, it's a firewall issue on your side.
Aspera uses TCP and UDP ports 33001. (by default).

---

2. Shares
   For Shares: place single quotes around the username and password, in case there are any special shell characters in those.
   In addition, for Shares: use of API is linked to use of Shares API.
   Shares API must be enabled for users:

So, in order to be able to use the CLI with Shares, you must be granted API access by Shares' admin.

[laurent-martin]

Note

This repository is not a general purpose support channel for IBM Aspera, it is only about ascli.

A typical "single node" Aspera Shares setup is composed with:

• A Linux VM
• with Aspera Shares installed on it
• with Aspera HSTS installed on it
• with local sshd daemon configured to listen on port TCP 33001.

So the typical ports in play are:

• TCP/443 for HTTPS for the web UI of Shares
• TCP/33001 for session contral of Aspera transfers (HSTS)
• UDP/33001 for file transfer (FASP, HSTS)

so, those ports must be reachable from client apps to the server.
This is true for ANY client app, including:

• a web user using browser + web client (Aspera Connect or Aspera for Desktop)
• a CLI user using ascli (which uses the aspera transfer sdk)

Another way to test ssh connectivity:

ssh -v xfer@demo.asperasoft.com -p 33001

In case of successful connection, the output includes:

...
debug1: Connecting to demo.asperasoft.com port 33001.
debug1: Connection established.
...
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 Ubuntu-3ubuntu0.13
...

You can try from another server that would have full internet access (or laptop, etc...)

If you don't get the banner it means that something in the middle is doing something... (firewall).
Nevertheless, we can see in the output you gave:

Trying 52.116.196.54...
Connected to demo.asperasoft.com.
Escape character is '^]'.

Meaning that a TCP connection is done, but the banner does not come back...

[laurent-martin]

Can you confirm you have solved your issue ?