Call unsuccessful after 8 tries. Retrying in 64 seconds
Hi, newbie here and I'm stuck in this problem. I've scan through google and here but found no good solution. Everything works fine in my localhost deployment but break in the vercel app deployment. The error only appear in larger files, uploading smaller file works fine. I've already updated my upload thing to the latest version and generated an updated api key, as well as disabled my vercel authentication, and redeployed my app multiple times. The file is being uploaded in my upload thing files and I can also see the file appear in my app dashboard.
13 Replies
Update: Still haven't found a fix to my problem, have zero errors on my code but the file is still stuck on the "Callback unsuccessful" loop in my vercel deployment.
is ur pdf file is above 16 MB?
No, the pdf I have uploaded is just 1MB
is there any other useful information in error console log? Can you open it please?
Yes it only shows this.
Also, the overiddeMethod shows this error.
Could not load content for webpack://react-devtools-extensions/react-devtools-shared/src/backend/console.js (Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME)
dang, works in localhost but not in production, But it does not work in production only with large files.
Also it shows in uploadthing dashboard
the only problem is that it throw error and not giving you successful status. It is indeed strange. Also i see you use default uploadthing component so you dont do back-end yourself
Yes this is strange, I already reached out to the uploadthing product feedback channel and now waiting for julius or markr replies, hopefully they can help me fix this problem.
GitHub
[bug]: file uploads work locally but not in production using the de...
Provide environment information System: OS: macOS 14.1.2 CPU: (11) arm64 Apple M3 Pro Memory: 62.03 MB / 18.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/n...
it looks familiar
Yes I also read this bug report in the repo and tried disabling the vercel authentication. But still didn't work. I think I need to wait for their response in the product feedback channel before I can continue the project
i see
good luck
@Alpaca hi Alpaca, I have the exact same issue. I have been searching all day with no soloution happy to work together to try fix it please keep me posted if you find the soloution.
fixed it 🙂 I moved my deployment from vercel to railway.app and re ran the production and it worked!! feels so freakin good