File gets uploaded locally but when trying on deployed version it gets stuck on redirecting about quill HOT 10 OPEN

I have this issue too. I'm not seeing the new file added in the database either.
I wonder if there's an issue in the onUploadComplete function in src/app/api/uploadthing/core.ts

from quill.

I have the same issue, Any updates or solutions?

from quill.

Versel works fine for me

from quill.

@willbrandin Yes, I have encountered the same issue, for some reason, it seems that onUploadComplete is not being fired in a production environment

from quill.

Could be an authentication issue, as I also get a 401 error just before the 404. Meaning the middeware before onUploadComplete might return an Unauthorized. But I also have not found a solution yet.

Edit: Ok, so apparently not an Authentication issue. In 'Dev' mode, uploadthing simulates a webhook, to notify the server, when the fileupload is finished. This is not done in 'production' environment. Still do not know how to solve it, but there is an issue on the uploadthing github: pingdotgg/uploadthing#474

from quill.

I finally got the file upload running on production by installing the new version of [email protected] and @uploadthing/[email protected]. Make sure to push and test directly on Vercel, not in the local npm build. Anyway, Uploadthing warns not to test callbacks on localhost. That is how I finally got it to work.

[UT] [WARN] You are using a localhost callback url in production which is not supported. Read more and learn how to fix it here: https://uploadthing.com/faq#my-callback-runs-in-development-but-not-in-production

from quill.

The uploadthing documentation has not been updated to reflect the new update. @m3phist can you show us where or what you changed in your code?

from quill.

I had the same issue, file uploading didn't work when deployed. It was stuck at the upload box loading. Looking at the logs, the api/trpc/getFile endpoint was being polled every few seconds and never stopped (also error 404).

Afterward, I noticed the file was successfully uploaded to UploadThing but it was NOT added to the database (thus the infinite polling), so the issue was the code to add the file to the database wasn't running (the code in the callback onUploadComplete in src/app/api/uploadthing/core.ts).

Turns out Vercel was the issue, it allowed a maximum of a few seconds of computing at a time so the uploaded file was never added to the database as the code to do it timed out. Thus, the infinite polling.

TLDR; the solution is to deploy elsewhere like Netlify or upgrade from the Hobby plan on Vercel.

from quill.

@gptsparky I'm having the same issue as you when I deployed my express app on railway. I am hosting my client in Vercel and currently using Preview Deployments. I've already did what UploadThing docs say about turning off Vercel Authentication Vercel preview deployments, unfortunately, it still didn't work for me.

It uploads the file to UploadThing but the onUploadComplete callback doesn't trigger which causes the loading on my client to not stop.

Upon viewing the logs from railway I saw this kind of error.

from quill.

in live file is not uploaded give me any solution

from quill.