Tunnel Not Found

tunnel-not-found · 404

The API found no tunnel by that id that the caller opened.

A tunnel belongs to the person who opened it, whatever the workspace: a teammate's tunnel answers this same 404.

Besides the members every error carries, this type adds resourceType and resourceId.

Common causes

  • Another person opened the tunnel.
  • The id has a typo in it.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • Open a tunnel of your own with POST /v1/services/<service>/tunnels.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

json
{
  "type": "tunnel-not-found",
  "title": "Tunnel Not Found",
  "detail": "Tunnel with ID '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' was not found",
  "resourceType": "Tunnel",
  "resourceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/tunnels/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "method": "DELETE",
  "instance": "DELETE /v1/tunnels/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/tunnel-not-found"
}