Intermittent 502/504 Errors with call createSignedUrl() in Supabase Storage API

[ihabdevteam]

Hello Supabase team and community,

I have been experiencing intermittent 502 and 504 errors when calling the createSignedUrl function in the Supabase Storage API. The issue occurs quite frequently, making it difficult to reliably generate signed URLs for accessing stored resources.

The storage contains short MP3 files (less than 10 seconds).
Client does not fetch multiple resource URLs at once; it retrieves one URL per request.
RLS (Row Level Security) is enabled to restrict access to authenticated users only.

I submitted a support request to the Supabase Support team on March 14, 2025 (Ticket ID: 21431502639), but I have not received any response yet.

I would like to ask if anyone else has encountered a similar issue. If so, have you found any solutions or workarounds? Any troubleshooting advice would be greatly appreciated.

Thank you in advance for your help! 🔥

[jimmy3574]

This is also happening to us. Started recently. Did they get back to you?

[ihabdevteam]

Following our initial report, we raised additional issues with the Supabase team regarding the following problems:

1. When attempting to delete multiple objects at once from the Supabase dashboard, 502 errors frequently occur, interrupting the deletion process.
2. Similar issues arise when trying to list objects using S3-compatible clients.
3. In some cases, even when accessing resources via public URLs, the same problems persist.

In response, the Supabase support team mentioned the possibility of issues occurring at the gateway level (such as Cloudflare) and also suggested that 504 errors during createSignedUrl requests might be related to insufficient JWT expiration times. They informed us that this was passed along to the Supabase Storage team. However, since their last message on March 25, we have not received any further updates or seen any concrete actions taken to resolve the situation.

Since March, we’ve been receiving continuous complaints from our users due to these issues. Given the instability, we determined that we could no longer expose our customers to such a poor experience. As a temporary solution, we developed a separate service using AWS S3, Lambda functions, and CloudFront to provide pre-signed URLs similar to createSignedUrl.

We believe that if more members of the community who are facing similar issues share their experiences, it may help raise visibility and push toward a faster resolution of this matter.

Have you tried any alternative solutions that worked for you?
It would be greatly appreciated if you could share them.