Skip to main content

​
Run the doctor

When something goes wrong, start with neetokb 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 a one-line error message and exits with a non-zero status.
Problem: no workspace is signed in.
Solution: run neetokb login --subdomain <name>.
Problem: more than one workspace is signed in, so the target is ambiguous.
Solution: add --subdomain <name> to the command. For neetokb logout, --all signs out of every workspace instead.
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: neetokb login found no NeetoKB workspace at <subdomain>.neetokb.com.
Solution: enter only the first part of your workspace URL. For https://acme.neetokb.com, the subdomain is acme. See Workspace subdomain.
Problem: the browser sign-in was not approved within two minutes.
Solution: run neetokb login again and approve the sign-in in the browser tab it opens. If no tab opens, paste the URL the CLI prints into your browser.
Problem: a required flag was omitted.
Solution: check the command’s reference page or run neetokb <command> --help for the required flags.
Problem: the CLI could not reach <subdomain>.neetokb.com.
Solution: check your network, then run neetokb doctor to confirm the API responds.
Problem: the saved session is no longer valid. The message ends with Suggestion: Authentication session expired. Run 'neetokb login' to re-authenticate.
Solution: run neetokb login --subdomain <name> again.
Problem: your account lacks permission for this action, such as creating or publishing an article.
Solution: ask a workspace admin for the required role, or sign in with an account that has it.
Problem: no record matches the ID you passed.
Solution: check the ID. Article commands accept a slug, permalink identifier (a-XXXXXXXX), or UUID. Team member commands accept the UUID shown by neetokb team-members list.
Problem: the server rejected the request, for example a validation error. Each further error the API returned is listed on its own line below the message.
Solution: fix the listed fields and retry. Run neetokb <command> --help for the accepted flags.
Problem: you sent too many requests in a short time. The message ends with Suggestion: Rate limited. Wait and try again.
Solution: wait a moment, then run the command again.
Problem: the article is still a draft, so it has no public URL to share.
Solution: publish it with neetokb articles update <id> --state published, then retry the unlisted link command.
API errors follow the pattern API error (<status>): <message>. The message comes from the server’s error, notice, or errors field, or falls back to the HTTP status text. For 401, 403, 404, 422, and 429 responses the CLI appends a Suggestion: line.

​
Check the version

Prints the CLI version, commit hash, and build date - useful when reporting an issue. If you are behind the latest release, upgrade with: