Storage API returning 500 / 42P01 on all uploads (Database confirmed healthy) #44294
Unanswered
Ari522-tech
asked this question in
Questions
Replies: 1 comment
-
|
DId you try a restart of the instance? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, the Storage API for my project is throwing a 500 Internal Server Error with DatabaseError: 42P01 (relation does not exist) whenever I try to upload a file via the JavaScript client.
I have exhaustively debugged this and confirmed:
The bucket exists and is set to public.
RLS policies for INSERT, UPDATE, DELETE, and SELECT are correctly configured on storage.objects.
There are no rogue database triggers in information_schema.triggers for the storage schema.
Reloading the PostgREST schema cache did not fix the issue.
Direct SQL inserts into storage.objects work perfectly.
Because direct SQL works but the API client fails, it appears my project's Storage API microservice container has a corrupted internal state or schema map. Could you please hard-reset the storage API container for my project?
Beta Was this translation helpful? Give feedback.
All reactions