Skip to main content
Solutions for common issues you may encounter while using Relic.

​
Session & Authentication

Your session token has a limited lifetime. When it expires, re-authenticate:
Session data is stored at ~/.config/relic/session.json. If the file is corrupted, delete it and log in again.
JWT tokens refresh automatically. If the error persists, clear your session and re-authenticate:

​
Secret Injection

Check the following:
  1. Verify the environment name matches exactly: relic run -e development -- ...
  2. Make sure relic.toml exists in your project root (run relic init if not)
  3. Clear stale cache:
The next relic run will fetch fresh data from the server.
Cache invalidation happens automatically when secrets are updated. If you still see old values, delete the local cache:
When using API keys (CI/CD mode), caching is disabled and secrets are always fetched fresh.

​
TUI

Relic’s TUI requires a terminal with true color support. Use one of these:You can verify your terminal supports true color:
If you see xterm or screen, your terminal may not support the full color range the TUI needs.
Run with debug logging enabled to see what’s happening:
Then check the log file:

​
Debugging

When something isn’t working, enable debug logs to get more information.
1

Enable debug logging

Set the RELIC_LOG environment variable:
2

Check the log file

Logs are written to ~/.config/relic/logs/:Override the log path with RELIC_LOG_FILE if needed.
3

Watch logs in real time

Tail the log file while running Relic in another terminal:

​
Cache

Relic caches data locally to reduce API calls. If you need to reset it:
Clearing the user key cache does not delete your encryption keys from the server. You will not lose access to your secrets.

​
Still stuck?

Open an issue

Report bugs or request features on GitHub.

Security issues

For security vulnerabilities, email us directly. Do not open public issues.
Last modified on October 8, 2026