Why Supabase Storage randomly gives 400 - Object not found error even though the file is present?

Hi everyone, as the title says, i am facing this problem since quite a time. I have .txt files present in a folder in supabase storage bucket, but every time i am trying to access the file through python backend (using , it gives me 400 - Object nor found error, even though the file is present at the exact spot from where i want to download. After few tries i am able to download it. Has anyone faced this issue too? And how you fixed it.

Information about my case:

Stores .txt file in a folder in supabase storage bucket.
Retrieves them from a backend in python.
Using free trial of supabase right now. (is that the problem? can't afford the pro right now as it is just for side quest)

let me know your views, and if u are facing, then comment for better reach please!!! that will help a lot!

garyaustin•1/16/25, 8:45 PM

Is it a public folder or private? If private then you likely are not meeting your RLS policy for some reason. You might check the session right before you download. I don't know Python so can't advise on the specifics.

Tanmay SharmaOP•1/16/25, 8:50 PM

Hey man, thanks for your reply. I didn't understand what you meant by private folder but i am guessing you mean private bucket. If that's the case, then yes its private. And for the RLS policies i have assigned that authenticated users can access it but i am accessing it from the backend using service_role key so i think RLS won't be a big issue. Plus it works sometime after retrying it for many times.

garyaustin•1/16/25, 8:52 PM

Right. Sometimes users have private and RLS work and not work because they lose the session in the client. In your case if you are service_role (and your client does not get a user session in accidentally) then it should bypass RLS.

garyaustin•1/16/25, 8:53 PM

Free instance is not actually a trial as many run real apps on it and it is not limited on access with any sort of symptom you describe.

Tanmay SharmaOP•1/16/25, 8:55 PM

Hmm then its a really weird problem that i am facing

will keep looking for solutions. But thanks man for your time!!

garyaustin•1/16/25, 8:56 PM

Check the API Gateway log to see if it is getting to Supabase and if the pathname matches your file...

Tanmay SharmaOP•1/16/25, 9:03 PM

Oh i didn't knew about this. will check. thanks!!

Tanmay SharmaOP•1/16/25, 9:04 PM

right now it is working, will have to wait for it to fail next time.

Tanmay SharmaOP•1/16/25, 11:30 PM

@garyaustin hey man, i have noticed one thing. I am launching my app in python debugger. So the first time i launch it, it fails. But when i make any code change (even a print statement), and the app restarts, then it works.

Tanmay SharmaOP•1/16/25, 11:31 PM

Also i checked the logs, and everytime the request failed, the user was authenticated using some authentication id instead of service role. So i am assuming that the issue might be with the initialisation of the client.

garyaustin•1/16/25, 11:36 PM

If you decode the jwt is it anon or a user jwt?

garyaustin•1/16/25, 11:36 PM

I won't be able to help with Python.

Tanmay SharmaOP•1/20/25, 5:22 PM

Hi @garyaustin , sorry for late response. Upon checking its a user jwt.

Tanmay SharmaOP•1/20/25, 5:23 PM

so the flow of my application requries first login and the user can perform some operation. to perform the operations, the backend will download the files from the bucket. the auth_user i am seeing here is the user i am using to login.

Tanmay SharmaOP•1/20/25, 5:24 PM

as my understanding it should not take the user login instead should use the service key

garyaustin•1/20/25, 5:25 PM

If you set service_role on a client but then allow it to get access to a user session it is no longer service_role.

garyaustin•1/20/25, 5:26 PM

Seems like you are sharing the user session in your service_role client.

Tanmay SharmaOP•1/20/25, 5:27 PM

yes that will be required. to fix that should i use different clients for handling user related queries and database related queries?

garyaustin•1/20/25, 5:27 PM

If you want service_role for a client then yes. Otherwise the client would be a user session client.

garyaustin•1/20/25, 5:28 PM

You can access the db as a user if you have RLS to allow it.

Tanmay SharmaOP•1/20/25, 5:29 PM

so now i have two options:

setup two different clients, one for accessing storage and one for handling user information.
setup rls on storage and use that for handling both queries by using only a single client
right?

garyaustin•1/20/25, 5:30 PM

Yes. Either is fine depending on your needs.

Tanmay SharmaOP•1/20/25, 5:30 PM

hmm, then good. Thanks a lot for your help man!!! You saved me a lot of time!!

Why Supabase Storage randomly gives 400 - Object not found error even though the file is present?

Similar Threads

Similar Threads

Similar Threads