Run the doctor
When something goes wrong, start withneetokb doctor. It checks your authentication, API connection, and CLI version.
Common errors
When a command fails, it prints a one-line error message.not logged in. Run 'neetokb login' to authenticate
not logged in. Run 'neetokb login' to authenticate
Problem: no workspace is signed in.
Solution: run
Solution: run
neetokb login --subdomain <name>.multiple subdomains logged in (acme, beta); specify --subdomain
multiple subdomains logged in (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 logged in to "foo". Logged in subdomains: acme, beta
not logged in to "foo". Logged in 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.
required flag(s) "xxx" not set
required flag(s) "xxx" not set
Problem: a required flag was omitted.
Solution: check the command’s reference page or run
Solution: check the command’s reference page or run
neetokb <command> --help for the required flags.Article must be published before an unlisted link can be generated.
Article must be published before an unlisted link can be generated.
Problem: the article is still a draft, so it has no public URL to share.
Solution: publish it with
Solution: publish it with
neetokb articles update <id> --state published, then retry the unlisted link command.An API error message
An API error message
Problem: the server rejected the request (for example, a validation error).
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.