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?
Bigwibyera Aristide is experiencing a 500 Internal Server Error with a DatabaseError 42P01 when uploading files via the JavaScript client to the Storage API. They have confirmed the bucket exists, RLS policies are correctly configured, and direct SQL inserts work. They suspect a corrupted internal state in the Storage API microservice and request a hard reset of the container.
DId you try a restart of the instance? There have been no reported outages. Support may be needed for this and you should file a ticket if you have not.