Error fetching log file from Supabase Storage
# support
r
I have setup Supabase Credentials in the Integrations to store the call logs and recordings. These credentials work because I can see call logs & mp3 files being stored in the Supabse Bucket. However, when I click on "Call Logs" from VAPI Dashboard, it throws an error Fetching Call Logs from Custom Storage! Steps already tried: 1. Making the bucket Public - didn't wotk 2. Tried to fetch the same URL from Postman, with AWS Auth - Works! It seems like then VAPI is fetching the call logs for Dashboard, it is not correctly adding the Auth to the GET request. Example: Call ID: 0199bd06-d34b-799b-bc55-1b1869e958ad Screenshots attached for reference. Please help asap - critical project delivery pending @Vapi Support Bot https://cdn.discordapp.com/attachments/1424991219544621107/1424991220077166744/image.png?ex=68e5f5fd&is=68e4a47d&hm=66842fdb39c9f7d8935f1ddfa51bcd63eec3ec329b13afa6a82174e29de73a66& https://cdn.discordapp.com/attachments/1424991219544621107/1424991220475891774/image.png?ex=68e5f5fe&is=68e4a47e&hm=d2563e1f42a4f576751178cf86f8c01442c57ab652a1f0de8e5893ef71537d70& https://cdn.discordapp.com/attachments/1424991219544621107/1424991220874215444/image.png?ex=68e5f5fe&is=68e4a47e&hm=7ca572d087b09124469c87f5d2e8c831cc32935f7707c9b37640b9c23c68ca21&
v
Hi, I can help you resolve this issue. From what you described, your Supabase credentials and bucket setup are correct since files are successfully stored and accessible via Postman. The error in the VAPI Dashboard likely means the dashboard isn’t correctly attaching authentication when fetching the call logs. To help you directly, I’ll need to know: Are you using the standard VAPI Dashboard fetch, or is this a custom setup?. @ronaks2309
r
Hi @Vercel Thank you for your prompt response. I am using standard VAPI Dashboard fetch. No custom setup. The only thing I did was I added my Supabase credentials in the "Integrations" section.
v
Thanks for confirming. Since you’re using the standard VAPI Dashboard, the issue likely comes from how the dashboard handles authentication when fetching from Supabase. I’ve fixed similar setups before and can help you resolve this directly. Let’s continue privately so I can check your configuration and get it working properly. @ronaks2309
r
Yes. That's what I think too. Let me DM you.