I'm getting a 403 on my local storage service (Docker). Request looks like this: http://192.168.1.119:5000/storage/v1/object/avatars/ Headers include authorization, apikey ( both ANON_KEY). I'm a bit clueless on this issue.. Everything looks fine in the config files. The fact that i'm getting a 403 indicates that the storage service is active and reachable. Anyone have any clue where i need to look? 🙈 The database and auth service work just fine.

Hello @Rickert! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates. Want to change the title? Use the ``/title`` command! We have solved your problem? Click the button below to archive it.

So you were able to create a bucket and had set the RLS policies to do that or are you using service key.

I’ll take a look in a minute. Thx for the help 😃

I use supabase-js, not the rest API directly. Unless you are saying that is your output from supabase-js?

I'm using supabase_flutter for a Flutter app. I've looked at several parts as can be seen on the screenshots. I believe i've correctly set up the RLS policies on the storage.object table as can be seen in the first screenshot.

just for later your update policy will need to be using and it can also have with check, but that will default to the using policy.

How could i do that? I tried the following but no luck "CREATE POLICY "Allow avatar uploads" ON storage.buckets FOR INSERT" Still 403.