Deployment link to vercel doesn't work
Unanswered
British Shorthair posted this in #help-forum
British ShorthairOP
There were no problems in the build command, however when I click on the link it shows this error on the console: Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.
49 Replies
which is a bug in your code that you need to fix
British ShorthairOP
well where can I find the mistake that's the thing
because in development I can't find a single error.
@British Shorthair because in development I can't find a single error.
You might try
npm run build and see if you can the error thereon your local environment
British ShorthairOP
I tried it
Damn
British ShorthairOP
it shows no errors
idk why but I hate when I have to deploy something
Ok so that would usually mean an Environment variable issue
British ShorthairOP
i actually
tried adding the variables to vercel
it still didn't work
You might find that the variables in vercel aren't always added into your .env file. which is annoying as hell.
British ShorthairOP
well now the page has a
504: GATEWAY_TIMEOUT errorI took all my variables from
.env and added them to Environment variablesidk if this is a nextjs or vercel problem
British ShorthairOP
would providing the source code help you
I just did it
now what
did you not just get an error
British ShorthairOP
nope
everything is fine
damnit I have a different issue now
British ShorthairOP
wait Imma deploy the updated package.json
thanks for helping me tho
British ShorthairOP
that's exactly the time
where I had the most problems
Well there you go
British ShorthairOP
you sure that's it
Well I was getting no errors until about that time myself, I am working on next auth deployment and my aws builds failed in almost the exact same way, no error, just that NPM failed. But have verbose logging enabled on AWS so was able to track it down to a MAIN REPO is down.
which would translate to a gateway timeout
British ShorthairOP
what alternatives can I try for nextjs
maybe vercel is the problem
vercel alternatives sorry
Unfortunatly.... no. The the repository for building the code is ran every time you build. That means that code cannot be run, and therefore builds fail.
And no, because the same thing is happening to me on AWS and on a privately held server that my friend lets me host with.
sitting duck
we just have to wait until npm is back up
can you help me with my problem?
British ShorthairOP
ok
@bwrtu1 can you help me with my problem?
get your own question post lol
i have