Skip to content

The v1 docs follow nauthera-server's main branch and its 0.x releases on the way to 1.0, so fields and APIs can still change.

v1

unavailable

Docs version v1 (main)Nauthera is pre-1.0, in a design-partner program

The feature is not available here, or something it depends on could not answer (503).

Meaning

  • The operation is not served by this deployment: the admin API, passkeys, consent, password reset, email verification, invitations or logout when not set up.
  • A dependency could not answer: a hosted captcha provider, the store behind sign-out or an organization's lookup (/orgs/{slug}/...), or the per-request rate limiter.
  • With audit.fail_closed: true, the audit pipeline is degraded and a privileged change (admin user and organization changes, second-factor changes) is refused before it is made.

Impact

For a feature not set up, it is permanent until configured. For a dependency, users may be unable to sign out, register or administer until it recovers; a sign-out refused this way means the user may still be signed in. It is a sign of an outage or misconfiguration, not normal operation.

Diagnosis

  1. Read detail: it names the feature, or says the audit log or captcha cannot answer.
  2. Look the request id up in the logs and on the Troubleshooting page; dependency failures are recorded with reason unavailable and a cause such as captcha_unverifiable, organization_lookup_failed or throttle_failed_closed.
  3. Check readiness (GET /readyz on :9090), which reports the database, and the cache and audit pipeline as soft dependencies; a degraded pipeline is recorded as system.audit.degraded.

Mitigation

  • As a user or client developer: retry later.
  • As an operator: restore the failing dependency, or configure the feature. For the audit pipeline see Audit Log; for a hosted captcha provider, check egress to it and its secret.

Escalation

Escalate when the dependency is healthy and requests are still refused, or the audit pipeline stays degraded. Open an issue with request ids, the log lines for them, the readiness output and the server version.

Problem code runbooks · Generated from internal/runbook/problems.yaml in nauthera-server.