-
Notifications
You must be signed in to change notification settings - Fork 116
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
Application error: a server-side exception has occurred (see the server logs for more information). #3775
Comments
@Jay2113 any help please |
Your problem may be in the environment variables. I had the same problem:
I solved it by changing the name of the environment variable Checks whether there is a variable with the incorrect name that vercel is unable to read. |
i am facing the same issuee it would be great if u help me bro |
send the log so I can help you with your error and the two environment variables, production and dev environment |
|
|
Guys whoever facing the issue please refer here https://discord.com/channels/752553802359505017/1167434854703579176 |
did u solve the issue bro? |
Yes, I did solved it |
Wait till tomorrow here already midnight so tomorrow I'll check my code-base and give the the code |
yes sir please it would be a great help me to...as i want to submit my project please try to provide me the code |
Sure please wait hehe |
were u deploying in vercel? |
Yes I did deployed on vercel as well as on aws |
Btw are you using nextjs or other framework? |
Next.js sir |
about the varible resend_api_key, which service are you using? Which service is not running in your production application? needing to identify which service is not working to investigate the configuration of its environment variable. Your problem is an environment variable that is not being read by Vercel due to an incorrect description, name or configuration. |
about resend_api_key sir...i am using resend.com service |
how do i check sir can u eloborate |
do u have any solution please provide me |
Just the https://resend.com/ email sending service is not working? Well, let's go. See here in one of my applications in which I use resend, see that I am using other variables, which are: the user |
i didnt get sir |
email service is working |
??? |
I need to know which service in your software is not working so I can help you. Until now I don't understand which service is not working causing that error. |
in locally the project just works fine...but while deploying in vercel it causes this error |
Are you using any authentication service in your application? like authjs? |
Are you using an ORM, like Prisma? |
using mongodb |
mongobd is database. Copy the contents of your package.json file here for me |
{ |
Now send me the content in the .env file (Remove the keys) |
sure wait |
PAYLOAD_SECRET= STRIPE_SECRET_KEY= RESEND_API_KEY= |
I don't know if you don't understand, but some client side service is not working due to some variable not being read by vercel in a production environment that's why it gives that error |
is it sure that because of this..resend.com variables not added thats why it is giving me the error |
Redeploy your application after adding the variables. You have to see that tutorial is old, and the requirements there do not resend production variables. |
okay sir i'll add the variables of env and let u know |
import dotenv from "dotenv" dotenv.config({ const transporter = nodemailer.createTransport({ let cached = (global as any).payload if(!cached){ export const getPayloadClient = async ({
} this is the code of resend.com please have a look.. |
but this code is back-end, right? your problem is client side. |
As I mentioned here, try to check which services you are using next to the client and consider adding NEXT or NEXT_ in front of the name of the environment variable in the vercel settings. And deploy it to your application to see if it works. |
oh i got ur point now... |
okay bro i will check this tomorrow..thank u so much for this help,..YOU ARE A GREAT GUY!!!! |
if any problem persists hope u willl help me :)..thank u once again |
Sir???? |
Application error: a server-side exception has occurred (see the server logs for more information). |
this error appear when you want to deploy your project . i used nextjs and supabase Enter Key-Value Pairs:
after entering this values pair , it would work , atleast for me , to locate where you would enter this values . To set your environment variables in Vercel, follow these steps: Guide to Setting Environment Variables in Vercel
Example of Adding Environment Variables Here's how it should look:
|
Don't know why but I m get server side exception error in my code can anybody let me know why is this happening. I have once tried deploying code on vercel it works fine but when I tried deploying the same code on aws amplify it through the Application server side accepting error can anybody help me out plz.... I m using nextjs with nextauth and mongodb |
Can you tell me how can I solve this issue if you already have solved it. |
I'm late to the party but I just experienced this issue using Next.js 14 and Supabase, my project is less than two weeks old and I spent some time trying to solve it. No other solutions worked for me until I found this link: https://supabase.com/docs/guides/auth/server-side/nextjs I had to change my middleware and create server client function |
Before opening, please confirm:
App Id
I'll ask my backend team and update it
AWS Region
ap-southeast-1
Amplify Hosting feature
Backend builds, Deployments, Frontend builds
Frontend framework
Next.js
Next.js version
13.5.3
Next.js router
App Router
Describe the bug
I have a next js app with next auth and it got deployed on aws amplify, and it's not working when it got deployed on aws amplify the app is really breaking and not even working and it's working on local.
It's nextjs app with the app router with next auth and backend with the graphql and deployed on AWS amplify
I'm getting the above errors
Here's my setup
next.config.js
auth.ts
route.ts
in app/api/auth/[..nextauth]amplify.yml
in the root folderExpected behavior
It should working without any errorsbe working
Reproduction steps
Build Settings
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: