Error reference

The edge received a bind without valid credentials.

Fix: Run /login inside the console, or set TRQSH_API_KEY / api_key in ~/.trqsh/trqsh.yml. Restart an existing daemon after changing startup credentials.

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: Use /update inside the console or reinstall through your original package manager. Use /down before relaunching the updated agent.

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

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

The account's transfer allowance for the enforced usage window is used up.

Fix: Check the account usage window, wait for allowance to become available, or choose a plan with more bandwidth.

This month's request allowance is used up.

Fix: Check this deployment's request allowance and usage window, then wait or choose a higher limit.

Another account has claimed that subdomain.

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

The requested name is not reserved by the account binding the tunnel, or reserved names are not permitted.

Fix: Use /subdomains reserve NAME or the dashboard's Domains page, then bind using the same account. Check reservation limits separately.

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 (for example UDP or a custom domain) isn't allowed by your effective plan.

Fix: Check the effective plan and its expiry, then use an allowed feature or upgrade. Protocol availability also depends on the edge deployment.

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

Fix: Use the documented HTTP, TCP or UDP workflow supported by your edge. Core HTTPS/TLS identifiers do not guarantee HTTPS upstream forwarding or SNI passthrough.

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

Fix: Choose an available port in the edge's configured pool, or omit remote_port. On a self-hosted edge, also publish/open the assigned port.

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).