Troubleshooting

Common CLI failure modes, in rough order of how often they come up.

celigo: command not found

The npm global bin directory isn't on your PATH.

npm bin -g      # prints the directory

Add it to your shell rc file:

# bash / zsh
echo 'export PATH="$(npm bin -g):$PATH"' >> ~/.zshrc

# Windows PowerShell (one-shot)
$env:Path = "$(npm bin -g);$env:Path"

Or re-install with a Node Version Manager (nvm, volta) that manages PATH for you.

401 Unauthorized

• Token is missing, expired, or revoked.
• You're pointing at the wrong region. A token authenticates only against its own region's base URL.

Inspect the active config:

celigo config show
celigo profile list

Rotate the token with celigo config set api_token <new> and retry. See Authenticate.

403 Forbidden

Token is valid but lacks the capability the request needs. Either broaden the token's scope in the UI, or switch to a profile whose token has admin access.

404 Not Found on a resource you know exists

• Wrong base URL — the resource lives in a different region's tenant.
• Wrong profile — check celigo profile list.
• Custom-scoped token doesn't see the resource (the API returns 404 Not Found to avoid leaking existence).

429 Too Many Requests

The HTTP client retries automatically with the server-supplied Retry-After. If you're still being throttled:

• Run with lower parallelism — serialize shell loops instead of xargs -P.
• Filter jobs list / audit list queries so they return fewer pages.
• Batch writes at the source rather than looping one POST per record.

See Rate limits in the API section.

Error: self-signed certificate in certificate chain

Behind a corporate proxy with TLS interception. Point Node at your organization's CA bundle:

export NODE_EXTRA_CA_CERTS=/path/to/corp-root-ca.pem

⚠️ Never disable TLS certificate validation. Do not set NODE_TLS_REJECT_UNAUTHORIZED=0 — it disables cert checking account-wide in your shell and is a silent-failure vector.

EACCES when installing globally

On macOS/Linux without sudo, the default global prefix isn't writable. Either:

# Use a user-local npm prefix
mkdir -p ~/.npm-global
npm config set prefix ~/.npm-global
export PATH=~/.npm-global/bin:$PATH
npm install -g @celigo/celigo-cli

Or use nvm / volta — both handle the prefix for you.

CLI says "A new version is available"

The CLI auto-updates every four hours on startup. If auto-update failed or you want to force it:

npm install -g @celigo/celigo-cli@latest

Suppress the check: export CELIGO_NO_UPDATE=1.

Still stuck?

• Re-run with --verbose — prints the underlying HTTP request/response (token redacted). Paste that into a support ticket along with celigo --version.
• Community: connective.celigo.com.
• Production incidents: status.celigo.com.