Supabase signed URLs returning 404
When I try to access any resources on my bucket, I get returned the following message:
The bucket is called 'assets'.
I have the following relevant policies:
1) Read access for all authenticated users
Basically
2) Give authenticated users access to the assets bucket
Generating a signedUrl via the JS api works, but I get the same issue when accessing the signed URL. I have tried changing my bucket to
Some relevant information:
1) This database is copied over from an existing database via pg_dump and pg_restore.
2) I nuke the
3) Interestingly enough, if a given user is the one who uploaded the file, they can access it. Otherwise, it returns a 404.
Any ideas how I can fix this?
The bucket is called 'assets'.
I have the following relevant policies:
1) Read access for all authenticated users
Basically
SELECT queries for authenticated role users return true directly.2) Give authenticated users access to the assets bucket
SELECT queries for authenticated users have the following check: ((bucket_id = 'assets'::text) AND (auth.role() = 'authenticated'::text))Generating a signedUrl via the JS api works, but I get the same issue when accessing the signed URL. I have tried changing my bucket to
public and using get URL from within the GUI, but I still get that issue.Some relevant information:
1) This database is copied over from an existing database via pg_dump and pg_restore.
2) I nuke the
public schema every now and then for tests, but I grant necessary privileges to service_role, auth, and authenticated roles on the public schema.3) Interestingly enough, if a given user is the one who uploaded the file, they can access it. Otherwise, it returns a 404.
Any ideas how I can fix this?
