Skip to main content

Start with doctor

neetodesk doctor checks each thing independently and reports all of them, so one failure does not hide the next:

Reading an API error

When the API rejects a request, the CLI reports the status code, the message the API returned and a suggestion:

Common problems

Problem: No workspace is signed in on this machine.
Solution: Run neetodesk login. See Authentication.
Problem: You are signed in to more than one workspace, so the CLI will not guess which one you meant.
Solution: Add --subdomain acme to the command, or drop the workspaces you no longer need with neetodesk logout --subdomain globex.
Problem: The subdomain you passed is not among the ones signed in. The message lists the ones that are.
Solution: Check the spelling of the subdomain, then run neetodesk login --subdomain acme.
Problem: The saved session token expired.
Solution: Run neetodesk login to sign in again. The stored credential is replaced.
Problem: The CLI could not reach the host at all, rather than being turned away by it. A proxy or VPN is the usual cause.
Solution: Run neetodesk doctor to see which host it is trying, and confirm you can reach that host in a browser.
Problem: The install directory is not on your PATH.
Solution: Open a new terminal. The installer edits your shell profile, which the running session has already read. See Installation.
Problem: The completion script on disk is the one the older version wrote.
Solution: Re-run neetodesk completion <shell>. See Shell completion.
Problem: The CLI acts as the person who signed in, so it is bounded by that person’s role. An agent restricted to their own tickets or to their groups sees a narrowed list.
Solution: Confirm which account you are signed in as with neetodesk whoami. If the account is right, the restriction is the role, not the CLI.

Getting the version

Include the version when you report a problem: