Replies: 12 comments 20 replies
-
|
Hey @hmtri1011, sorry to hear you're having trouble with this. Could you provide us with a minimal reproduction or the source code if public? That'll help us investigate this from the Vercel side. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Sorry, I cannot share the source code :(. This issue only happens in re-build time (I cannot replicate on my localhost). I will give you the realtime screenshot on my dashboard, it includes the error and folder output.
As you can see the task to load "/designed-in-california" was timed out even though I have this page on my output folder |
Beta Was this translation helpful? Give feedback.
10 replies
-
|
Hi @MyLokaal, I just deploy my site to my real server :p |
Beta Was this translation helpful? Give feedback.
-
|
@mcsdevv Can I share with you my source code? Maybe you'll be able to tell what could fix that issue. Here's my repo: https://github.com/MyLokaal/mylokaal. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
@Khristinasheer this is almost certainly due to a problem with your MongoDB configuration or query. You are not getting a response in time and so the function is timing out. You need to add further logging to understand why this is the case. |
Beta Was this translation helpful? Give feedback.
-
|
hey bro, I was having the same problem, I was trying to use an api for vercel. However, when I made the request from my api it exceeded the processing limit, so the vercel server automatically closes the request (error 504 ). The purpose of my application was for the frontEnd to send the data to my api and the backEnd of my application hosted on the vercel server, to send this data to another place, be it a database or to an email. I did a lot of research, performed several tests with Postman Canary and saw that it was a simple thing... :/ even if I don't want to access the api, just send it to it, it is necessary that this api gives a response to the server, because it's no use doing a request and in that request execute several lines of code and you will not have an answer. So just return an answer with anything, it can even be in Json: module.exports = (req, res) => { if it is an asynchronous process use: module.exports = async (req, res) => { // api response to the server to end the process and avoid the 504 error |
Beta Was this translation helpful? Give feedback.
-
|
Looks like we've hit the Hobby plan limits, as of 1/2023. |
Beta Was this translation helpful? Give feedback.
-
|
:) I love Vercel, it is great, but you are so scrimp. That's true, Heroku free give no limit for that. Vercel can't upload file more than 5MB too, even I want pay to get that, but they say NO :D |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
That's not really a fair comparison. Heroku gives you always-on containers, Vercel gives you serverless functions. A better comparison would be AWS Lambda which has a 6MB payload limit, but then you need to deal with AWS. |
Beta Was this translation helpful? Give feedback.
-
|
I'm in the same predicament right now. I'm still developing and am saving refactoring for later. The repository url is here: The main directory is: Screenshot of Error
Build LogsScreenshot of Function Log Details
|
Beta Was this translation helpful? Give feedback.
4 replies
-
gonna explore: accordions & performanceI'm currently trying and exploring accordion optimization as potential source of problem
|
Beta Was this translation helpful? Give feedback.
-
adding a single line fixed it for now... more optimization to come in the future
|
Beta Was this translation helpful? Give feedback.
-
|
A new problem exists: an internal 500 error. I changed the index file, and the function logs show different screenshot of page error
more build logsfunction logs
some more function logsI also tried to implement Lighthouse for performance monitoring. |
Beta Was this translation helpful? Give feedback.
-
the error continueReal time logs in Functions Logs |
Beta Was this translation helpful? Give feedback.
-
|
ok now we know what is the problem, but how we can handle the error, I tried _error.js and 500.js and none of those catches that error anyway, seems like it shows 504 in production and there is no way to handle it |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have the same problem, even in production. It's really really boring. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I also have the same problem. Even upgrading Heroku. In other words, I'm not using a free plan.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm experiencing the same issue: Source code: https://github.com/hamza1311/dear-diary-web https://github.com/hamza1311/dear-diary-web/blob/nextjs/src/pages/api/login.ts#L9 https://github.com/hamza1311/dear-diary-web/blob/nextjs/src/pages/index.tsx#L185-L187 What can be done to debug what's happening? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm also randomly hitting this issue. I'm using mongoose in an API endpoint so I thought it had to do with reconnecting to the db, but I added logs to track the time it takes to await the db promise and it is consistently under one second. I'm starting to think this is just a problem with Vercel and there's nothing I can do... My mongoose connection code is here and my failing API is here. If someone at Vercel could check either of these correlation ids it would be really helpful:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm using elasticsearch in my api endpoint and I'm getting these random errors too. I try to retrigger the exact request in production and cannot get the same 504 error. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
it's very good to know there are so many guys who meets the same problem, I have been stuck in this for almost a whole day...... and I have consulted the vercel people, and they always say it was my upstream service problem, but actuall not, becasue I can run this nextjs ISR service well in locally, which shares the same upstream service as the one on vercel did,,,, and the funny thing is that, there is no request coming in my upstream service when refreshing frontend page on vercel (using ISR) I THINK THE BEST SOLUTION IS TO DEPLOY IT ON A REAL SERVER! |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Truth! Nor are they themselves, I have a plan to explain with Vercel and I have already asked support for help and they have not been explained properly. Several errors where the Heroku api had no errors and responded far below 1 second. (Note: I also have a paid plan on Heroku, so my dyno doesn't sleep) |
Beta Was this translation helpful? Give feedback.
-
|
Same issue. Locally the api response from my deployment backend is lightning fast. But Vercel stills times out. |
Beta Was this translation helpful? Give feedback.
-
|
Hey y'all! There are a few different things to check regarding serverless function timeouts. Please feel free to give the checklist a once-over. Otherwise, if issues persist (on Vercel, and not locally) feel free to reach out either via the Vercel Community Discussions or, for paid plans, via our helpdesk, providing as much information as possible (request path, function name and HAR files, where possible)! |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Adding to this topic.
|
Beta Was this translation helpful? Give feedback.
-
|
In fact I just added a simple // pseudo code of what I wrote
await Promise.race([notion.database.query({...}), new Promise((res)=>setTimeout(() => { console.log("timed out on slow Notion API response"); res(); }, 3000))]) |
Beta Was this translation helpful? Give feedback.
-
|
Ended up using Heroku, the problem doesn't occur there. The speed difference is slight, but that's better than stale site. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My site has been used ISR and has ~100 static generation pages. It did work well, but when the static pages need to be revalidated (2 minutes in my case), sometimes NextJS cannot generate those static pages, and my page becomes empty content (this is weird because if cannot generate new static pages, then old static pages must be used).
The next weird thing is this issue doesn't always happen, I'm not sure whether it is Vercel host or NextJS issue.
Above is the log I got from Vercel dashboard and my site within that error (no contents at all).
Any helps would be appreciated, thank guys!!
System information
Beta Was this translation helpful? Give feedback.
All reactions