Skip to main content

Terminal unavailable

typehttps://docs.frem.sh/reference/api/errors/terminal-unavailable
HTTP status503 Service Unavailable

What it means

Terminal access is not configured on this deployment: the relay URL or its signing secret is absent, so no usable ticket can be minted.

The API answers 503 rather than returning a well-formed ticket that nothing would accept. A ticket signed with no secret looks valid to a client and is refused at the relay, which presents as “the button works and the terminal never opens” — a far harder thing to diagnose than an explicit refusal.

Example detail messages returned with this error:

  • Terminal access is not configured on this deployment.

What to do

Nothing to retry on the client. On fremforge-hosted plans this is ours: check status.frem.sh or email support@frem.sh. On a self-hosted deployment, the relay URL and signing secret both have to be present.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/terminal-unavailable",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "..."
}

Branch on type, not on title or detail - those are human-readable and may be reworded.

Tenant scope requiredTest failed