Errors
tunnel_port_pool_exhausted
503 – No raw-TCP port free.
No raw-TCP port free. Answered with 503.
What it means
The deployment allocates a Tunnel's own raw-TCP port from a pool of numbers, and every one of them belongs to another Tunnel – or the deployment runs no pool at all. Nothing about the Tunnel changed: it still serves HTTP, WebSocket and raw TCP by SNI on the collector port, which needs no number of its own.
What to do
Reach the Tunnel over TLS with SNI on tunnel.sni_port instead, which is the other raw-TCP way in and is never rationed. Release a port an Identity no longer dials with DELETE /api/identities/{handle}/tunnel/tcp-port, or ask support@tigby.eu to widen the pool.
The body
{
"type": "https://tigby.eu/problems/tunnel_port_pool_exhausted",
"title": "No raw-TCP port free",
"status": 503,
"detail": "…what was refused, naming this request's own values",
"code": "tunnel_port_pool_exhausted",
"doc_url": "https://docs.tigby.eu/errors/tunnel_port_pool_exhausted",
"agent_hint": "…the next step, for software"
}Branch on code. The detail names this request's own Handle, id or limit and is not part of the contract.