How do you troubleshoot Remote CLI?

Use this guide for common Remote Command Line Interface (CLI) setup, authentication, permission, and command issues. The CLI is intended for customers who are comfortable using a terminal. The Remote dashboard remains the recommended option for visual, everyday work.

If you have not installed and configured the CLI, follow the Remote CLI quick start before troubleshooting.

The CLI returns a 400 Unauthorized error

This error includes 400 in the error message. It usually means your Remote role or authentication credentials do not allow the requested action.

1. Confirm that you signed in to the intended Remote account.
2. Confirm that you selected the intended company.
3. Check whether your role permits the same action in Remote.
4. Review the command's authentication and permission requirements in the developer documentation.
5. Contact your Remote administrator if you need different access.

The CLI is using the wrong company

If you have access to more than one company, run remote use and select the company you want to work with. Then run the command again.

Before changing data, confirm that the selected company is correct.

A command is not recognized

1. Run remote --help to review the commands available in your installed version.
2. Run remote <command> --help to review the expected syntax and options.
3. Compare your installed version with the version covered by the developer documentation.
4. Check spelling, spaces, and required arguments in the command.

Browser sign-in does not complete

When you run remote login, the CLI opens a browser page so you can approve access.

If sign-in does not complete:

1. Confirm that your browser opened the Remote sign-in page.
2. Sign in with the intended Remote account.
3. Complete the approval flow in the browser.
4. Return to the terminal and check the result.
5. Review the authentication guide if the issue continues.

Before contacting Remote Support

Include:

• The command you ran, with secrets removed
• The full error message, with personal or sensitive information removed
• The approximate time the issue occurred
• Your CLI version
• Your operating system and terminal
• The authentication method you used, without sharing credentials

Never send an API token, partner token, password, or other secret in a support request.

Related articles

• See also: Getting started with Remote CLI
• See also: How does Remote CLI authentication and access work?
• See also: What can you do with Remote CLI?