Run the doctor
When something goes wrong, start withneetoauth doctor. It checks your authentication, API connection, and CLI version.
Common errors
When a command fails, it prints a one-line error message.Not authenticated. Run 'neetoauth login' to authenticate.
Not authenticated. Run 'neetoauth login' to authenticate.
Problem: no workspace is signed in.
Solution: run
Solution: run
neetoauth login --subdomain <name>.Multiple subdomains authenticated (acme, beta); specify --subdomain.
Multiple subdomains authenticated (acme, beta); specify --subdomain.
Problem: more than one workspace is signed in, so the target is ambiguous.
Solution: add
Solution: add
--subdomain <name> to the command.Not authenticated for "foo". Authenticated subdomains: acme, beta.
Not authenticated for "foo". Authenticated subdomains: acme, beta.
Problem: the
Solution: use one of the listed subdomains, or sign in to the new one.
--subdomain value doesn’t match any signed-in workspace. Solution: use one of the listed subdomains, or sign in to the new one.
--email is required
--email is required
Problem:
Solution: pass
users create ran without an email address. Solution: pass
--email <address>, or supply it in the file given to --json-file.--role is required (e.g. owner, non_owner)
--role is required (e.g. owner, non_owner)
Problem:
Solution: pass
users create ran without an organization role. Solution: pass
--role owner or --role non_owner. This is the organization-level role, not a product role.Invalid --app value "neetocal" (expected name:role).
Invalid --app value "neetocal" (expected name:role).
Problem: an
Solution: write it as
--app value is missing the role half. Solution: write it as
name:role, for example --app neetocal:admin. Run neetoauth products list to see the valid pairs.An API error message
An API error message
Problem: the server rejected the request (for example, inviting someone who is already an active member, or removing the last owner).
Solution: the CLI passes through the server’s message. Check the JSON envelope (or
Solution: the CLI passes through the server’s message. Check the JSON envelope (or
--quiet payload) for error, errors, or notice and any suggestions from the API.Permission errors
The CLI acts as the person who signed in, so commands are checked against your own permissions. If a command fails with an authorization error, ask a workspace owner to grant you the permission, or use an API key against the REST API instead.Check the version
neetoauth update to move to the latest release.