CLI issues

Updated on 18 Feb 2025
1 Minute to read

Print
Share
Dark
Light
PDF

Article summary

Did you find this summary helpful?

Thank you for your feedback

CLI Troubleshooting

If you're having trouble with CLI commands or functionality, this could be due to installing the CLI in an unsupported method. Only the documented method (Install the CLI) is supported. Any other method could lead to issues with CLI commands.

If you did a yarn install, complete the following steps:

Use the yarn remove command to remove the erroneous CLI installation.
In a new directory, use npm install and follow the documented workflow in Install the CLI.

Error Messages

The following are error messages you may encounter when using the CLI.

Command: any

Error: Command not found
Resolution: Upgrade to the new CLI.

Command: login

Code	Response text and description	Resolution
`400`	`E-mail is not verified.`	Verify that you have included the required parameters.
	`Must include either "email" or "password".`
	`Provide a valid token.` This only occurs when logging in with a one-time password.
	`Unable to log in with provided credentials.`
	`User account is disabled.`	Verify your permissions with your organization administrator.
`403`	`Too many failed login attempts. Please wait 1 (one) hour and try again.`	Verify your credentials and then try logging in after at least one hour.
`500`	`Internal error`	Contact Crowdbotics Customer Support.

Command: publish

Code	Response text and description	Resolution
	`git_url: The provided git URL is not accessible`	The URL is incorrect or Crowdbotics does not have permission to reach the specified repository. Verify that the URL is correct. Check repository visibility. If the git repo is private, be sure to include the private access token within the URL. Verify that the token has the required permissions to read the private repo. For more information, refer to Publish your modules.
`400`	`Modules cannot be published because no organization was chosen. Please select an organization to promote the modules to its catalog.`	Verify that you have included the required parameters.
`400`	`Task ID not provided`	Verify that you have included the required parameters.
`401`	`Unauthorized to access the resource`	Log out and log in again.
`403`	`Only authorized team members can publish modules to the selected organization.`	Verify your permissions with your organization administrator.
`404`	`Organization does not exist`	Verify that you have included the required parameters.
	`Project not found`
	`Task ID not found`
`422`	`Publish module failed due to payload validation`	Contact Crowdbotics Customer Support.
`500`	`Error publishing module due to an internal server error`	Contact Crowdbotics Customer Support.

Was this article helpful?

What's Next

Upgrade to the new CLI

Table of contents

CLI Troubleshooting
Error Messages