”No api_key found in callback. Exiting.”
The authentication flow didn’t complete properly. How to fix:“API Key Verification Failed” / “Fetch Failed”
This usually indicates a network or configuration issue. Common causes and fixes:- Check your network connection — ensure you can reach
api.getunbound.ai - Corporate proxy — if behind a corporate proxy, configure proxy settings in your terminal
- Verify environment variables are set correctly:
Both should return values. If empty, your shell profile didn’t load them — re-add them and run
source ~/.zshrc.
”Self-Signed Certificate Detected”
This occurs when your corporate network uses SSL inspection or interception. Fix: Add your corporate CA certificate to Node.js:~/.bashrc, ~/.zshrc, or PowerShell profile). Contact your IT team for the correct certificate file path.
”Claude Code Not Found” After Installation
Node.js/npm Version Issues
If you updated Node.js or npm and Claude Code stopped working:- Reinstall Claude Code:
- Verify the installation:
- If using
nvm, make sure the correct Node.js version is active
Token Limit Exceeded Errors
If you see “Claude’s response exceeded the output token maximum”, set the environment variable to increase the limit:Still Having Issues?
API Key Troubleshooting
Fix invalid API key errors
Model & Token Errors
Resolve model and token limit issues

