Error · 409

shell_not_enabled

Shell access is not enabled for this account

What happened

Shell access has not been switched on for this hosting account, or the key that was authorised is no longer accepted.

What to do

Call manage_shell_access with action=enable for the same account. The customer approves it once, then the command can run.

The response body carries a recovery object with the same guidance in machine-readable form: recovery.action names the call to make next, and recovery.hint is one sentence a model can act on. Not every code carries one — a 401, for instance, has nothing to recover to but a valid token.

conflict — The request conflicts with the current state
hosting_not_ready — The hosting account is not ready yet
attempt_replayed — This attempt key has already been used
quota_exceeded — Quota exceeded

Back to the full error reference

409 application/problem+json

{9 keys}

:"https://api.inleed.com/errors/shell_not_enabled",

:"Shell access is not enabled for this account",

:409,

:"Shell access has not been switched on for this hosting account, or the key that was authorised is no longer accepted.",

:"shell_not_enabled",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

:"2026-08-29T12:34:56.000Z",

:{2 keys}

:"…",

:"Call manage_shell_access with action=enable for the same account. The customer approves it once, then the command can run."

}

Click a key to copy its jq path.

Handling it

// Branch on code, never on title or detail — those are written for
// humans and may change wording at any time.

if (problem.code === 'shell_not_enabled') {
  // Call manage_shell_access with action=enable for the same account. The customer approves it once, then the command can run.
}

What happened

What to do

Other 409 responses