Critical: Auth 500 errors caused by authenticator role configuration

Hi Supabase team,

My hosted Supabase project’s Auth service is broken due to an issue with the authenticator role, and I can’t fix it from the dashboard.

Project

URL: https://hovyxvvmzkkeyklfzhqx.supabase.co

Project ref: hovyxvvmzkkeyklfzhqx

Region: EU (Ireland), Plan: Free

Issue

All Auth operations (login, signup, password recovery) return HTTP 500, e.g.:

Database error querying schema

On /auth/v1/recover: Unable to process request

Diagnosis

The authenticator role has no USAGE on the auth schema.

authenticator is NOINHERIT and only a member of anon, authenticated, and service_role, so it does not inherit their privileges.

Because of this, queries to the auth schema from Auth fail.

I tried ALTER ROLE authenticator WITH INHERIT and GRANT USAGE ON SCHEMA auth TO authenticator, but both fail because only superusers can modify this reserved role.

Request

For project hovyxvvmzkkeyklfzhqx, could you please either:

set authenticator to INHERIT, or

grant USAGE on schema auth to authenticator,

to restore Auth functionality?

Impact

Severity: critical

Auth is completely non-functional

All users are affected

The project is currently blocked for development and use

Thank you very much for your help,
Was this page helpful?