Supabase•14mo ago•

4 replies

Supabase signed URLs returning 404

When I try to access any resources on my bucket, I get returned the following message:

{"statusCode":"404","error":"Not found","message":"The resource was not found"}

{"statusCode":"404","error":"Not found","message":"The resource was not found"}

The bucket is called 'assets'.

I have the following relevant policies:
1) Read access for all authenticated users
Basically

SELECT

SELECT

queries for

authenticated

authenticated

role users return true directly.
2) Give authenticated users access to the assets bucket

SELECT

SELECT

queries for

authenticated

authenticated

users have the following check:

((bucket_id = 'assets'::text) AND (auth.role() = 'authenticated'::text))

((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

public

and using

get URL

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

public

schema every now and then for tests, but I grant necessary privileges to

service_role, auth, and authenticated

service_role, auth, and authenticated

roles on the

public

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?

Supabase signed URLs returning 404

When I try to access any resources on my bucket, I get returned the following message:

{"statusCode":"404","error":"Not found","message":"The resource was not found"}

{"statusCode":"404","error":"Not found","message":"The resource was not found"}

The bucket is called 'assets'.

I have the following relevant policies:
1) Read access for all authenticated users
Basically

SELECT

SELECT

queries for

authenticated

authenticated

role users return true directly.
2) Give authenticated users access to the assets bucket

SELECT

SELECT

queries for

authenticated

authenticated

users have the following check:

((bucket_id = 'assets'::text) AND (auth.role() = 'authenticated'::text))

((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

public

and using

get URL

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

public

schema every now and then for tests, but I grant necessary privileges to

service_role, auth, and authenticated

service_role, auth, and authenticated

roles on the

public

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?

Supabase signed URLs returning 404

Similar Threads

Supabase signed URLs returning 404

Similar Threads

Similar Threads

Similar Threads