Split the signals first
Quota or rate limits usually surface in dashboards or as HTTP 429. Credentials and permissions map closer to HTTP 401, missing tokens, or gateway denials. Local environment issues—ports, proxies, TLS, or permission regressions—can leave the app running while every model call times out.
The primary entry remains the connection troubleshooting guide. This article only documents the common mix-ups around quota and upgrades.
Quota and throttling: avoid noisy retries
- Note what triggered the burst: manual runs, cron jobs, or batch automations stacked together.
- On 429, pause script-style loops; confirm the provider’s window and policy first.
- Separate “client error text” from “account balance”—they are not always the same root cause.
- Quotas will not be fixed by unverified installers; stay with verified download sources.
Post-update failures: diff the change list
- Did config paths move? Do secrets need re-importing?
- Did permission scopes tighten? Automation grants may reset after upgrades.
- Are external hooks or browser extensions still compatible with the new build?
- Read the current release notes for breaking changes that require manual migration.
“Cannot connect to the model”—which layer failed?
- Can the machine reach the public internet (DNS, proxy, corporate firewall)?
- Is the provider reporting incidents or regional limits?
- Is a local port conflict present? Errors such as EADDRINUSE deserve their own branch.
- If you switched vendors, verify base URLs, scopes, and regional availability.
Linking pricing, download, and platform checks
Some quota questions belong with pricing notes that separate “depends on external services” from hard promises. Install and rollback questions return to the download page and platform verification notes.
Quota and update FAQs
Is “quota exhausted” the same as “cannot reach the model”?
Often not. Quotas and rate limits usually show up as HTTP 429 or provider dashboards. Connectivity can still fail due to network, proxies, keys, or local port conflicts. Capture the exact error text before choosing a fix path.
After an update it stopped working—should I reinstall immediately?
Not always. Updates can change config locations, permission scopes, or secret handling. Diff what changed, read the current release notes, and then decide whether a clean install is warranted. This site does not promise a single magic command.
Does HTTP 401 mean my account was stolen?
Not necessarily. 401 commonly means credential or permission mismatch: expired keys, wrong scope, or provider policy changes. Verify the key source and service status rather than assuming a security incident every time.
Open the connection troubleshooting guide
Capture exact errors and boundaries before deciding whether to adjust models or your machine.
Connection guide FAQ