Realtime 401 error in Nextjs

[pablojsx]

I'm starting to think this is a bug because no matter what I do I always get a 401 error. I already have a setup for uploading images to their bucket and works fine, tried to use the same supabase instance and didn't work. I keep reading and I found about the ssr client, cool, no luck.

I have tried every youtube video, docs, no luck. I see a guy in stackoverflow having the same issue, it just return 401 all the time, RLS enabled with all policies combinations, disabled, no luck.

Is this a bug?

[pablojsx]

All combinations, around 6hrs, all I get is "Error 401: Unauthorized"

[pablojsx]

It's been 9 days of emails and supabase still won't fix this issue, which at this point comes from them since I've done everything available and it's dumb because it isn't even hard to make this work but for me it's just 401.

[pablojsx]

Dear diary, supabase sent me an email suggesting the use of a policy I used in day 1 .... it's been 2 weeks of nonsense.

._.

[ladderschool]

Same thing!

[GaryAustin1]

401 can be grants are missing on the schema or tables. This usually comes up if something like Prisma is used. Prisma during migrations can delete the grants so the API no longer has access. This would also though mean any select operations from next.js would not work.

A policy of anon also means an authenticated user will not have access. But with row level security disabled the RLS is not involved.

[pablojsx]

Hello Gary, can you give more details about the grants? I'm using Prisma and Nextjs. I also get 401 with the Supabase inspector.

[GaryAustin1]

See the trouble shooting section here for some code to fix the grants if that is your issue.
https://supabase.com/partners/integrations/prisma
Prisma during migrations often wipes out Postgres grants to the public schema.

grant usage on schema public to postgres, anon, authenticated, service_role;

grant all privileges on all tables in schema public to postgres, anon, authenticated, service_role;
grant all privileges on all functions in schema public to postgres, anon, authenticated, service_role;
grant all privileges on all sequences in schema public to postgres, anon, authenticated, service_role;

alter default privileges in schema public grant all on tables to postgres, anon, authenticated, service_role;
alter default privileges in schema public grant all on functions to postgres, anon, authenticated, service_role;
alter default privileges in schema public grant all on sequences to postgres, anon, authenticated, service_role;

[ladderschool]

That fixed it for me, that's exactly what it was since I was using Prisma. Thank you!

[mark-antal-csizmadia]

This worked, thanks!

[stpn48]

Oh wow, thanks bro worked for me ❤️. Just copy paste those commands into supabase SQL editor for anyone wondering.