Tidelift CLI Troubleshooting
With the wide variety of environments that the CLI can run in, there are some things which are easy to self-diagnose before reaching out for additional support
- Ensure that you are on the latest version of the Tidelift CLI. You can check the current version by visiting https://download.tidelift.com/cli/tidelift-cli.version and compare to the current installed version by running
tidelift version. We regularly update the CLI with fixes and improvements. Information on upgrading is found at the bottom of the installation doc.
- Ensure that you can reach the Internet from your machine (either developer workstation or CI system). Running
curl https://api.tidelift.com/subscriber/healthcheckshould include OK in the response (Linux/Mac only)
- Ensure that the Tidelift CLI can access the internet by running
tidelift selftest --repo test
- Ensure that you’re using a correct API key and that the key has not been revoked. The most common case of key revocation is that your trial has ended.
- If you are running scan or align and it fails with Exit status 1 but no other information, we may be unable to generate a lockfile. Manual instructions for each platform are as follows but may give more errors than you see exposed from the tool.
pip freeze --local
mvn -Dstyle.color=never dependency:list -DoutputFile=maven-resolved-dependencies.txt
- Other ecosystems do not have to generate a lockfile at this time