Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Client uploads to Vercel Blob fail with Vercel Blob: Access denied, please provide a valid token for this resource, specifically for larger files (up to 500MB) using client-side upload with handleUploadUrl. Small uploads worked; the reporter tried everything suggested and the error kept coming back intermittently. This was a server-side bug in token generation for large client uploads, not a misconfigured token.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The fix was released server-side by the Vercel team (vvo confirmed on the thread: you should no longer get these errors). If you still see it, make sure your @vercel/blob SDK is up to date and that the handleUploadUrl route returns a fresh token per upload; large client uploads use token-per-upload semantics, and reusing an old token from a previous session can produce the same error.
Source: https://github.com/vercel/storage/issues/541
Shows how to fix vercel Blob client upload: Access denied, provide a valid token. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix googleapis Node client does not auto-refresh the access token ("Invalid Client" after expiry). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes Intercom API 401 'The access token provided is invalid'.