Troubleshoot CLI authentication and transfers

CLI errors become easier to isolate when you reduce the task to version, authentication, context and one harmless listing request.

Before you start

• Use the current released client or web app and sign in to the intended account.
• Select the correct workspace and use non-confidential test data.
• Record the current setting or result before changing it.
• Keep passwords, API keys, recovery keys and private links out of screenshots and support messages.

Steps: troubleshoot cli authentication and transfers

1. Run version and built-in help.
2. Confirm authentication status and account.
3. List and select the workspace again.
4. Run one harmless list command.
5. Compare a failed transfer with role, quota and destination policy.
6. Retry only after correcting the identified boundary.

Expected result

The troubleshoot cli authentication and transfers workflow completes for the test item and its result remains visible after a refresh or reconnect.

Limits and important details

• Available controls depend on the current client version, plan, role and workspace policy.
• A successful connection does not grant permissions beyond its credential and workspace boundary.
• Verify important results with a harmless test before relying on the workflow.

Troubleshooting

The expected control is missing. Confirm the current client, active workspace and role, then check the relevant settings page.

The operation is rejected. Read the exact error and compare credentials, permissions, quota and workspace policy.

The result is still unclear. Repeat with one small test item and contact private support with the time, client version and nonsecret error.

Related guides

• Install the CLI
• Authenticate the CLI
• Select a workspace