Error reference

The edge received a bind without valid credentials.

Fix: Run `trqsh login`, or set `TRQSH_API_KEY` / the `api_key` field in `~/.trqsh-uz/trqsh.yml`.

The API key or token was rejected.

Fix: Create a fresh key in the dashboard under API keys and update your config.

This edge no longer supports your agent's protocol version.

Fix: Update the CLI: `trqsh update` or reinstall from the download page.

You've hit the number of simultaneous tunnels your plan allows.

Fix: Stop an unused tunnel, or upgrade for a higher concurrent limit.

This month's transfer allowance is used up.

Fix: Wait for the monthly reset, or upgrade for more bandwidth.

This month's request allowance is used up.

Fix: Wait for the monthly reset, or upgrade for a higher request ceiling.

Another account has claimed that subdomain.

Fix: Pick a different subdomain, or omit it to get a random one.

Reserved subdomains require an entitlement your plan lacks, or you've used them all.

Fix: Reserve the subdomain in the dashboard, or upgrade for more reserved slots.

The custom domain hasn't completed DNS verification.

Fix: Add the TXT and CNAME records shown in the dashboard, then re-verify.

The feature you requested (e.g. UDP or TLS tunnels) isn't included in your plan.

Fix: Upgrade to a plan that includes it — the error names the plan required.

The tunnel protocol you asked for isn't available on this edge.

Fix: Use one of http, https, tls, tcp, or udp.

The requested TCP/UDP remote port is already in use.

Fix: Choose another port, or omit `remote_port` for an ephemeral assignment.

You're opening connections or making requests too quickly.

Fix: Back off and retry; upgrade for a higher rate limit if you hit it often.

Something went wrong on the edge.

Fix: Retry shortly. If it persists, check status or contact support.

The edge reached your agent, but the agent couldn't connect to your local service.

Fix: Confirm your local server is running on the address you tunneled (e.g. `localhost:3000`).