Local supabase-nextjs-user-management with Supabase CLI returns 406 Errors

Question

I'm using Supabase CLI and nextjs-user-management sample.

After creating a user using the Next.js auth flow, I see 406 responses after loading the account screen, as well as with any attempts to update the user's data. I have not made any changes to the codebase. Anything I can look into here? (I'm new to Supabase)

If I change my .env.local NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY values to point to values on supabase.com (rather than local values), things work, so it seems related to a local configuration?

the response looks like:

{
    "code": "PGRST106",
    "details": null,
    "hint": null,
    "message": "The schema must be one of the following: "
}

brianc · Accepted Answer · 2024-12-12 00:31:57Z

0

It turned out the sample I was using did not have the correct values for schemas and extra_search_path inside config.toml. They should look like:

schemas = ["public", "graphql_public"]
extra_search_path = ["public", "extensions"]

answered Dec 12, 2024 at 0:31

brianc

1,6493 gold badges18 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Local supabase-nextjs-user-management with Supabase CLI returns 406 Errors

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related