No profile, key, or session
Symptom:tc doctor reports a missing profile, missing key, or missing session.
Fix: Start with profile setup and sign in.
Browser auth did not open
Symptom:tc auth login cannot open a browser callback.
Fix: Use paste mode or suppress the popup.
TC_OPENKEY_HOST or the profile’s openkeyHost.
Node health check fails
Symptom:tc node health says the node is unreachable.
Fix: Confirm the host and check the health endpoint.
TC_HOST and the profile’s host value.
tc doctor and tc node health disagree
Symptom: tc doctor reports the node as unreachable, but tc node health
or a direct /healthz request succeeds.
Cause: The current CLI commands probe different paths: tc doctor checks
the legacy /health path, while tc node health checks the node’s implemented
/healthz endpoint.
Fix: Use tc node health or /healthz as the node-health check and treat
the tc doctor node result as CLI drift. Continue using tc doctor for its
local profile, key, session, and space checks.
Space is not hosted
Symptom:tc kv or tc sql reports that the target space is not hosted.
Fix: Host the owned space before retrying the data command.
tc space info or tc space list to confirm the resolved space URI.
Secrets network is missing
Symptom:tc secrets doctor reports that the encryption network does not exist.
Fix: Create or reuse the default network.
A permission request is waiting
Symptom: You created a request artifact, but the action still fails. Fix: Inspect local state and retry once the requested capabilities are covered.Where to look next
tc doctorfor a quick local diagnostic passtc statusfor local profile and permission statetc auth capsfor coverage detailstc secrets doctorfor secrets-specific checks
These fixes are based on the CLI’s actual error hints and command behavior, not on hypothetical error codes.
