Skip to main content

​
Run the doctor

When something goes wrong, start with neetodesk doctor. It checks your authentication, API connection, and CLI version.
When multiple workspaces are signed in, name the one to check:

​
Common errors

When a command fails, it prints an error message to standard error and exits with status 1. Usage errors such as an unknown flag or a missing argument add Run 'neetodesk --help' for usage.
Problem: no workspace is signed in.
Solution: run neetodesk login --subdomain <name>.
Problem: more than one workspace is signed in, so the target is ambiguous.
Solution: add --subdomain <name> to the command. For logout, --all signs out of every workspace.
Problem: the --subdomain value does not match any signed-in workspace.
Solution: use one of the listed subdomains, or sign in to the new one.
Problem: neetodesk login could not find a workspace at <subdomain>.neetodesk.com.
Solution: use the first part of your workspace URL. For https://spinkart.neetodesk.com, enter spinkart.
Problem: the browser sign-in was not approved before the session expired. NeetoDesk CLI authentication timed out after 5 minutes. Please try again. means the CLI stopped waiting.
Solution: run neetodesk login again and approve the sign-in in the browser. If the browser does not open, visit the URL the CLI prints.
Problem: the CLI could not reach the API.
Solution: check your network and run neetodesk doctor. If NEETODESK_BASE_URL is set, confirm it points at a reachable server.
Problem: a required flag was omitted.
Solution: check the command’s reference page or run neetodesk <command> --help for the required flags.
Problem: the server rejected the request. The CLI prints API error (<status>): <message>, one line per additional error, and a Suggestion: line for common statuses: 401 (sign in again), 403 (no permission), 404 (check the ID), 422 (check required fields with --help), and 429 (rate limited, wait and retry).
Solution: follow the suggestion. For 401, run neetodesk login to refresh the session.
Problem: the CLI acts as the person who signed in, so an agent restricted to their own tickets or to their groups sees a narrowed list.
Solution: check which account is signed in with neetodesk whoami. If the account is right, the limit comes from the role. See What the CLI can reach.
Problem: neetodesk setup claude requires Claude Code to have been run at least once.
Solution: install and open Claude Code, then run the command again.

​
Check the version

Prints the CLI version, commit hash, and build date - useful when reporting an issue. To upgrade, run neetodesk update.