Troubleshoot the Fencer CLI
Overview
Section titled “Overview”Most CLI failures are missing organization context, an expired or missing login, an origin
mismatch, or an outdated binary. Start with fencer version and fencer org list.
Common issues
Section titled “Common issues”organization slug is required — use --org <slug> or set FENCER_ORG — pass --org <slug> or
set FENCER_ORG. fencer org list shows slugs you can access.
not logged in — run 'fencer login' first — no saved login and no FENCER_TOKEN. Run
fencer login, or set FENCER_TOKEN (see Authentication).
token refresh failed — run 'fencer login' again — the saved OAuth session can no longer be
refreshed. Run fencer login again.
API error 403 with Service account token has expired., … has been revoked., or
Invalid service account token. — the token in FENCER_TOKEN or your saved login no longer
works. Create a new service account under Settings > Service Accounts and use its token.
Your client version (…) is below the minimum required version (…). Please upgrade. — the API
answered 426 Upgrade Required because your binary is below its minimum version. Follow
Upgrading.
stored credentials are bound to a different API origin — you passed a --base-url that does
not match the origin you logged in to. Drop --base-url, or run fencer login --base-url <url>
for the new origin. The CLI connects to https://app.fencer.dev by default.
… — pass --yes (-y) to confirm in non-interactive mode — a write command ran without a
terminal to prompt on (for example in CI). Add --yes once you are sure of the change.
authorization timed out — fencer login waited 5 minutes without the browser approval
completing. Run it again; if the browser does not open, open the URL the CLI prints.
CI token scope — FENCER_TOKEN is only ever sent to the configured API origin
(https://app.fencer.dev by default).
Checksum mismatch — re-download the archive and SHA256SUMS from the same release. Do not
run a binary that does not match.
command not found: fencer — the install directory is not on PATH. The install script
prints the directory it used (/usr/local/bin, ~/.local/bin, or your FENCER_CLI_DIR) and says
when it is missing from PATH.
Support expectations
Section titled “Support expectations”Fencer Support covers the supported platforms listed in Installation: the official binaries, checksums/signatures, authentication against Fencer, and the documented commands.
Support does not cover unofficial builds, patched binaries, unsupported OS/architectures, or
wrapping the CLI in an unattended way that violates the software license (LICENSE) shipped in
each archive.
When you contact support@fencer.dev, include:
fencer version --output json- The exact command and the error text
- OS and architecture
- Whether you are using OAuth or a service-account token (do not send the token)