Skip to main content
Start with the doctor command:
Apply safe local fixes:

​
rye command not found

Confirm the install directory is on PATH. Default user installs use:
Add it for zsh or bash:
Restart your shell and verify:

​
Not logged in

Check auth state:
Sign in:
If rye up starts login automatically, complete the browser flow and return to the terminal.

​
Daemon is not running

Check daemon state:
Start or restart it:
Read logs:

​
No traffic is captured

Check these first:
  • Start the agent after setting proxy variables or use rye wrap.
  • Confirm rye status shows the proxy is running.
  • Confirm the target domain matches your intercept patterns.
  • Check whether NO_PROXY excludes the target host.
  • For GUI apps, use --auto-configure-proxy or launch the app from a shell that has proxy variables.
  • Use --intercept-all temporarily to separate pattern issues from routing issues.
Example:

​
TLS or certificate errors

Verify the CA exists:
Install the CA:
For Node-based tools, confirm NODE_EXTRA_CA_CERTS points to the Rye CA. rye wrap injects this when the CA exists. For tools with product-specific trust variables, set the documented CA variable manually:
Avoid disabling certificate verification except in a disposable test shell.

​
App shims are not taking effect

Run:
The shims directory must appear before the real app directories on PATH. For zsh or bash:
Restart your shell, then check:

​
System proxy did not restore

Stop Rye:
If the daemon is not reachable, restart it and stop again:
Then inspect your OS proxy settings. Rye can only restore settings it configured during the current proxy lifecycle.

​
Policy blocked a request

Blocked requests return 403 with a JSON body that includes:
  • request_id
  • decision
  • rule_id
  • rule_version
  • reason
Inspect recent history:
Use the request_id to correlate the block with local logs and control-plane events.

​
History is empty

Check whether:
  • The proxy is running.
  • The request domain matches intercept patterns.
  • The app is using the proxy.
  • The request is model API traffic, not package manager, Git, browser, or unrelated network traffic.
  • You are querying the right time window.
Try:

​
Need support

Email security@rye.ai with:
  • rye version
  • rye status --json
  • rye doctor --json
  • The command you ran.
  • The exact error message.