Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] I've been getting errors after deploying with Vercel. #308

Open
1 task done
jaychoubaby opened this issue Aug 13, 2024 · 4 comments
Open
1 task done

[BUG] I've been getting errors after deploying with Vercel. #308

jaychoubaby opened this issue Aug 13, 2024 · 4 comments

Comments

@jaychoubaby
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

image

Expected Behavior

Application error: a client-side exception has occurred (see the browser console for more information).

I have looked into similar questions, but I couldn't find an answer.

Steps To Reproduce

After I input the message, this error pops up during the response process.

Environment

chrome 127.0.6533.99

Anything else?

No response

@miurla
Copy link
Owner

miurla commented Aug 13, 2024

Have you checked the Vercel Runtime Logs?
https://vercel.com/docs/observability/runtime-logs#view-runtime-logs

@irosyadi
Copy link

I got the same error. Redis setup is obligatory. After setting the environment variables UPSTASHREDISRESTURL and UPSTASHREDISRESTTOKEN, the error is gone.

@miurla
Copy link
Owner

miurla commented Aug 27, 2024

@irosyadi Thank you for sharing.
Those error messages will also be output to Vercel's error logs. First, please check both the client and server error logs.

@jaychoubaby
Copy link
Author

I got the same error. Redis setup is obligatory. After setting the environment variables UPSTASHREDISRESTURL and UPSTASHREDISRESTTOKEN, the error is gone.

Adding these two properties does make it work properly, but occasionally it still throws errors. My understanding is that I shouldn't need the history because it relies on Redis, and UPSTASHREDISRES doesn't seem very stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants