Troubleshooting
Resolve connection, identity, model catalog and authorization issues.
My agent gets a 401 or cannot reach the local port
Confirm that TeeProxy's proxy is running and the listening address and port match. For a 401, check that the agent's key exactly matches the local key in Agent Connection. User IDs, platform identities and upstream tokens cannot replace it. If the connection is refused, check the process and port availability.
Can I skip a failed TEE verification?
Check the Router address, matching TDX / SNP policy, client version, system clock and network connectivity. Read the verification diagnostics. After a deployment upgrade, use a confirmed replacement policy. Do not disable verification or broaden the policy blindly to suppress an error.
The model does not exist or no accounts are available
Copy the full model ID again from TeeProxy and confirm that the agent protocol matches the provider. Check your balance, merchant access, fixed pool selection, multiplier ceiling, allowed models and capacity. Raising a multiplier ceiling affects costs; review prices first.
Basic requests work, but an agent feature returns 404
Agents may call additional endpoints. Current integration focuses on HTTP Responses / SSE and Anthropic Messages. Endpoints such as /responses/compact, /messages/count_tokens may not be supported. Check TeeProxy's client compatibility notes and version, and use the HTTP configuration in this guide.
TeeMerchant shows an account but no available models
Check that the account is enabled, its connection test passed and synchronization completed. Then check that the pool's model allowlist is not empty. Creating a pool, saving local credentials or seeing an account in the catalog does not by itself complete publication.
Authorization fails or an account expires later
Check the account's network proxy, then reauthorize through the provider's official flow. Confirm that the service is running and automatic renewal is enabled. An access token without valid renewal credentials requires reauthorization or updated import data when it expires.
My local ID or authorization data cannot be read on a new computer
Local identities and credentials include data protected by the operating system or machine-local keys. Preserve the full data directory and original decryption environment, and follow the client's migration procedure. Do not overwrite your only backup. On Windows in particular, copying protected files to another computer does not automatically make them decryptable.
When reporting a problem, include the client version, failing step and an error message with sensitive information removed. Do not include API keys, OAuth tokens, proxy passwords or local identity private keys.