Troubleshooting
Common issues, causes, and fixes.
Wrong master passwordWeb app (app.meowpass.dev)Cause
The salt stored on the server doesn't match your local CLI salt. This happens when mp login is run multiple times, regenerating the salt each time.
Fix
Clear your browser localStorage for app.meowpass.dev (or just the meowpass_salt key), then log in again. The web app will fetch the correct salt from the server. If the issue persists, run mp login from the CLI — it now reuses your existing salt.
mp pull fails for team memberCLICause
The vault hasn't been shared with the team using X25519 key exchange, or the team member hasn't set up their encryption keys yet.
Fix
The vault owner needs to share the vault with the team. Each team member needs to have run mp login at least once to generate their X25519 key pair.
decrypt vault key failedCLI or Web appCause
Wrong master password, or the vault was shared but your X25519 keys aren't set up. The CLI tries AES decryption first (own vaults), then falls back to X25519 (shared vaults).
Fix
Make sure you're using the correct master password. If this is a shared vault, re-run mp login to regenerate your X25519 key pair, then ask the vault owner to re-share.
vault limit reached, upgrade to ProCLI or APICause
Free tier is limited to 3 vaults and 50 secrets. You've hit the vault limit.
Fix
Upgrade to Pro ($3/mo) for unlimited vaults and secrets. Or redeem a promo code if you have one.
secret limit reached, upgrade to ProCLI or APICause
Free tier allows 50 secrets total across all vaults.
Fix
Same as vault limit — upgrade to Pro or redeem a promo code.
secret not foundWeb app or CLICause
The secret exists under a different environment. Secrets are scoped by env (default, local, production, etc.).
Fix
Check which environments have secrets, then specify the correct one.
No MeowPass project configuredCLICause
The CLI can't find a .meowpass.yaml file in the current directory or any parent directory. This file links a repo to a vault.
Fix
Run mp init in your project root to create the config file, or specify the vault manually with --vault.
No encryption key found. Please login via CLI first.Web appCause
Your account doesn't have a key_salt set. This happens if you registered on the web app without ever running mp login from the CLI.
Fix
Run mp login from the CLI. This sets up your master password, generates encryption keys, and uploads the salt to the server.
Empty activity logWeb appCause
Audit logging only tracks actions performed after the feature was deployed. Existing vaults and secrets created before have no audit trail.
Fix
Perform any vault or secret action (set, delete, rotate, share) and it will appear in the activity log.
API key invalid or expiredMCP server or CI/CDCause
The API key was revoked, or it was never created. API keys start with mp_ prefix.
Fix
Create a new API key and update your MCP or CI/CD config.
Still stuck?
Join our Discord server for help, or open an issue on GitHub.