Solutions to the most common issues with the Krypt CLI. If your problem isn’t listed here, email support@krypthq.com.
”krypt: command not found” after install
Cause: npm’s global bin directory is not in your shell’s PATH.
Fix: Find npm’s prefix and add it to your PATH:
Add <prefix>/bin to your shell profile (~/.zshrc, ~/.bashrc, or equivalent):
export PATH="$(npm config get prefix)/bin:$PATH"
source ~/.zshrc.
”EACCES: permission denied” on install
Cause: npm is trying to write to a system-owned directory.
Fix: Either install with sudo:
sudo npm install -g @kryptorg/cli
”Not authenticated” when running commands
Cause: Your API key is invalid, expired, or was revoked.
Fix: Log in again with a valid key:
krypt login --key krypt_live_<your-key>
”Project ‘X’ not found”
Cause: The project doesn’t exist on Krypt, or your account doesn’t have access to it.
Fix: Check which projects you can access:
If the project isn’t listed, create it in the dashboard or ask the project owner to invite you.
”Members cannot directly edit production secrets”
Cause: Your role is Member and you’re trying to push to production.
Fix: Members must submit a change request for production edits. Use the dashboard to propose the change, then ask an Owner or Admin on your team to approve it.
If you need direct production access, ask the project owner to upgrade your role to Admin.
”Failed to fetch” / network errors
Cause: The Krypt API is unreachable — firewall, DNS, or proxy issue.
Fix: Verify the API is up:
curl https://api.krypthq.com/api/health
export HTTPS_PROXY=http://proxy.company.com:8080
Secrets pulled but .env shows old values
Cause: You pulled from the wrong environment, or secrets were updated after your last pull.
Fix: Pull from the correct environment explicitly:
Use krypt diff to compare what’s different between environments:
krypt diff --envA development --envB staging
Still stuck?
Email support@krypthq.com with:
- Your CLI version (
krypt --version)
- The full command you ran
- The complete error output
