Access Control Not Enabled

access-control-not-enabled · 404

Access control is off on this Ghaym deployment, so the API neither reads nor changes who may open a service.

It is a 404 so that a console or the CLI that asks hides the access section rather than show a gate nothing enforces. Staging an access change is refused the same way.

This type adds no members to the ones every error carries.

Common causes

  • The deployment runs with access control off, which is the default until an operator turns it on.
  • The access of a service was read, or a change to it was staged, such as with ghaym cloud access set <service>.

How to fix the call

  • Leave access alone: it can't be read or changed here until an operator turns it on.
  • Tell the user if they need a restricted or private service, quoting detail.
  • Don't retry: the answer won't change on its own.

Example response

json
{
  "type": "access-control-not-enabled",
  "title": "Access Control Not Enabled",
  "detail": "Access control is not enabled on this deployment.",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/access",
  "method": "GET",
  "instance": "GET /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/access",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/access-control-not-enabled"
}