If you are on a computer connected to a Google WiFi router, you may run into an edge case where any network request times out. This is a known issue and one we are actively working on solving. In the meantime, you patch the issue by changing the DNS settings on your computer to use
As an example, running
asdfasdf on macOS or Windows produces error output indicating the command doesn't exist, but
doppler run — asdfasdf doesn't produce any output (although it does still return the non-zero exit code).
If the error output is desired, use the form
doppler run --command="your-command-here" instead.
Interrupting a process on Windows with Ctrl + C will likely result in a non-zero exit code.
If you experience the error "Token not found in system keyring", then your local CLI token has gotten out of sync and will need to be reset before you can log in again.
First, find out what the scope of your current CLI token is by viewing the current CLI tokens and scoped locations:
Use value in the SCOPE* column associated with the token row and use that to unset the token. For example, if my token was scoped to /, then the command would be:
doppler configure unset token --scope /
Now you can login again:
If you're still experiencing issues, you can run the following command to reset the CLI back to its clean initial state by running:
# Use as a last resort as this will completely reset your config doppler configure reset
If the Shell Script install command is failing silently, you can enable debug output which may enable you to self-diagnose the issue (e.g. no outbound network connection) or provide to us in the event further troubleshooting is required:
# Shell Script debug install (curl -Ls --tlsv1.2 --proto "=https" --retry 3 https://cli.doppler.com/install.sh || wget -t 3 -qO- https://cli.doppler.com/install.sh) | sh -s -- --debug
Updated 2 months ago