OverviewInstallFirst commandAuthenticateInject secretsTerminal UIExport dotenvGenerate TOTPAutomateCommandsTroubleshooting
TROUBLESHOOTINGTroubleshooting

CLI troubleshooting

Use these messages to fix common errors before opening the TUI or rotating tokens.

Error: Not logged in.

Cause: there is no saved PAT and MOVITERA_TOKEN is not set.

bash
$ movitera login
# or
$ export MOVITERA_TOKEN=mvt_pat_xxx

Error: No team selected.

Cause: the command needs a team and is not running in an interactive terminal where it can open the picker.

bash
$ movitera team use <team-slug>
# or
$ movitera secrets pull --team <team-id> -c myapp-prod
# or
$ export MOVITERA_TEAM=<team-id>

Multiple credentials share that name.

Cause: run and secrets pull use the by-name ENV_BUNDLE endpoint, so duplicate names cannot be resolved safely.

  • Rename one credential in the web app.
  • Use movitera creds list --env --search <name> to confirm the final name.
  • Run the command again with -c <name>.

That credential isn't an env bundle.

Cause: run and secrets pull only accept ENV_BUNDLE credentials.

bash
$ movitera creds list --env
$ movitera run -c <env-bundle-name> -- <cmd>

This credential has no OTPAUTH_URI field.

Cause: the credential has no TOTP seed configured in Vault.

Fix: add the OTPAUTH_URI field to the credential in the web app, then run movitera totp <credential-id> again.

Next

AuthenticateCommand reference