Troubleshooting

Common problems with the Mixpost CLI and how to fix them. To see exactly what the CLI sends and receives, run the failing command again with --debug.

Symptom	Likely cause and fix
no workspace selected (exit code 2)	No workspace is set for the profile. Run mixpost workspace list, then mixpost config set workspace <uuid>, or pass -w on the command.
401 / exit code 3	The key is missing, mistyped, expired or revoked. Run mixpost auth login again and paste a new key. If MIXPOST_PERSONAL_KEY is set in your shell, it takes priority over the profile, so check it too.
403 / exit code 4 on create, update or delete	Your role in that workspace is Viewer, which can only read. Ask a workspace admin for the Member or Admin role.
404 on every command of a self-hosted instance	The address is missing the core path, or has the wrong one. Use the address you open Mixpost at in your browser, for example https://example.com/mixpost, and log in again.
The CLI can't connect to a self-hosted instance at all	The API may be turned off. Check that MIXPOST_API_ACCESS_TOKENS is not false in the instance's environment variables.
The commands work on the wrong workspace	Run mixpost config list to see the active profile's workspace, and mixpost auth status to see which profile is active. MIXPOST_PROFILE or --profile may be choosing another profile.
ping returns 404	ping exists only in self-hosted Mixpost Pro. On Cloud and Enterprise, check the connection with mixpost auth status.
Certificate errors	The instance uses a self-signed or expired certificate. Fix the certificate, or add --insecure on a network you trust.
A delete command says "this is not an interactive terminal"	Commands that delete things don't run without confirmation in a script. Add --yes.
Exit code 6 when scheduling a post	The post doesn't meet a requirement of one of its platforms, such as needing media. The error lists every requirement under requirements.<scope>.<provider>.<rule>. Fix the post and try again.
no account matches "…"	No connected account has that id, uuid, username, name or provider. The error lists the accounts you can use. See them all with mixpost account list.
--media expects numeric ids	--media takes the numeric id of a file, not its uuid. Find it in the id column of mixpost media list.
A scheduled post went out at the wrong hour	A time without an offset is read in your Mixpost user timezone. Pass --tz, for example --tz Europe/Chisinau, or use an RFC 3339 time with an offset.
macOS says the binary "cannot be opened"	A binary downloaded through a browser is unsigned, so Gatekeeper blocks it. Install with Homebrew or the install script instead.