Troubleshooting

Suggested troubleshooting order

When a Codex-style client cannot access the Codebyby relay, do not change many things at once. Check items in a fixed order.

Is the base URL correct?
Is the key valid?
Is the model name available?
Are the headers complete?
Is the client using the wrong proxy or stale cache?

Problem 1: Cannot connect

Check these first:

whether the current domain is still valid
whether the machine can reach the relay
whether the docs domain was mistakenly used as the API endpoint
whether the path prefix was omitted

Problem 2: Authentication failure

Check these first:

whether the full key was copied correctly
whether the Authorization header format is correct
whether the key expired, was disabled, or belongs to another instance
whether the client is reading the wrong key

Problem 3: Model request failure

Check these first:

whether the model name matches the current instance support
whether the client still uses an old default model
whether quota, policy, or rate limits blocked the request

Problem 4: Only one tool fails

If terminal requests work but one IDE or plugin fails, first inspect:

the tool's own proxy settings
cached local configuration
a separate address or key stored in the plugin panel
extra headers or compatibility-layer settings

What to prepare before contacting support

approximate time of the issue
client name
masked key identifier
target model
error response, log snippet, or screenshot

Continue reading