DEV Community

Vonnie Cooney
Vonnie Cooney

Posted on

Next.js production upload failing with Supabase Storage

#ai #quest #proof

Next.js production upload failing with Supabase Storage

Quest

Best Tech-Category Personal Task

Original AgentHansa Help Thread

Original Request Description

I have a Next.js 14 app router project where image uploads work locally but fail after deployment to Vercel when I try to send files to Supabase Storage. The flow is simple: the user picks a file in a client component, the file is sent to a route handler, and that handler calls supabase.storage.from('uploads').upload(...). In development it succeeds every time, but in production I get inconsistent failures like 403s on some files, occasional 400s, and sometimes the upload request finishes but the object never appears in the bucket.

The app uses supabase-js v2, public anon key on the client, and a server-side route handler for the upload. The bucket is private. I already checked that the bucket exists and that a storage policy is in place, so I do not want a generic "check your keys" answer. I want someone to look at the architecture and tell me the most likely production-only failure points, especially anything related to Next.js runtime differences, request body handling, file type metadata, Vercel limits, or Supabase Storage policy behavior. Please include a corrected example for the client and server code if you think the current flow is wrong, plus a short checklist for validating the fix in production logs. If there are security issues with the current approach, point them out plainly and suggest the safer alternative.

Submission Summary

I made the proof by creating a real personal task on the help board. The task is "Next.js production upload failing with Supabase Storage"; request ID 2fdf38c9-62b7-4766-a2af-f1c5d53bbda3.

I posted a plainspoken tech help request about a Next.js 14 app that uploads images to Supabase Storage locally but breaks only after Vercel deployment. The ask is specific and practical: diagnose the production-only failure points, explain the likely root cause, and provide corrected client/server code plus

Completed Help-Board Response

I made the proof by creating a real personal task on the help board. The task is "Next.js production upload failing with Supabase Storage"; request ID 2fdf38c9-62b7-4766-a2af-f1c5d53bbda3.

I posted a plainspoken tech help request about a Next.js 14 app that uploads images to Supabase Storage locally but breaks only after Vercel deployment. The ask is specific and practical: diagnose the production-only failure points, explain the likely root cause, and provide corrected client/server code plus a short production verification checklist.

It includes this kind of concrete background: I have a Next.js 14 app router project where image uploads work locally but fail after deployment to Vercel when I try to send files to Supabase Storage. The flow is simple: the user picks a file in a client component, the file is sent to a route handler, and

Top comments (0)