Connection Closed
Unanswered
Great black wasp posted this in #help-forum
Great black waspOP
there is no problem at development, but why is this happening in production environment
7 Replies
@Great black wasp there is no problem at development, but why is this happening in production environment
Polar bear
Experiencing the same issue.
Hey, have you figured out this problem?
West African Lion
looking for a solution for the same problem! If it helps mine happens when calling redirect inside a server action
Mugger Crocodile
It seems like if the load time is more than a given time, the timeout happens. This problem happened just couple of days ago. Are you using hobby plan?
@Mugger Crocodile It seems like if the load time is more than a given time, the timeout happens. This problem happened just couple of days ago. Are you using hobby plan?
West African Lion
Well I am actually not using vercel at all! I only tried it by serving locally. From what I've experienced the error only appears on the built version of the site.
The dev server runs perfectly fine. My speculation is that because the dev server is slow to compile each page at runtime some client side processes has enough time to complete themselves, where in the built site the pages loads too fast for its own good. Does this make sense? lol I really don't even know how to debug this when I don't even know what's causing it.
So far I've tried removing everything on the client page other than the form itself and everything on the server other than the
The dev server runs perfectly fine. My speculation is that because the dev server is slow to compile each page at runtime some client side processes has enough time to complete themselves, where in the built site the pages loads too fast for its own good. Does this make sense? lol I really don't even know how to debug this when I don't even know what's causing it.
So far I've tried removing everything on the client page other than the form itself and everything on the server other than the
redirect(). This has shown me that the redirect function is what causing the error (or atleast have something to do with it)I also have a function that fetches user info from a db in my root layout. Can that be causing any issue?
West African Lion
I think I solved my issue. What I did was remove bun from my project. Turns out, out of all things bun's password hash functions is what was causing the error. I suggest if anyone of you also use bun try removing it? Now I use @node-rs/argon2 instead of bun.password