#Deployment link to vercel doesn't work

50 messages · Page 1 of 1 (latest)

magic phoenix
#

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.

marsh wedgeBOT
#
Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

      🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in <id:customize>

      ✅ You can mark a message as the answer for your post with `Right click -> Apps -> Mark Solution`
      (if you don't see the option, try refreshing Discord with Ctrl + R)
knotty mural
#

which is a bug in your code that you need to fix

magic phoenix
#

well where can I find the mistake that's the thing

#

because in development I can't find a single error.

vestal crest
#

on your local environment

magic phoenix
#

I tried it

vestal crest
#

Damn

magic phoenix
#

it shows no errors

#

idk why but I hate when I have to deploy something

vestal crest
#

Ok so that would usually mean an Environment variable issue

magic phoenix
#

i actually

#

tried adding the variables to vercel

#

it still didn't work

vestal crest
#

You might find that the variables in vercel aren't always added into your .env file. which is annoying as hell.

magic phoenix
#

well now the page has a 504: GATEWAY_TIMEOUT error

#

I took all my variables from .env and added them to Environment variables

#

idk if this is a nextjs or vercel problem

vestal crest
#

Its not you!

#

Its NPM

magic phoenix
#

would providing the source code help you

vestal crest
#

try running a simple npm update command

magic phoenix
#

I just did it

#

now what

vestal crest
#

did you not just get an error

magic phoenix
#

nope

#

everything is fine

vestal crest
#

damnit I have a different issue now

magic phoenix
#

wait Imma deploy the updated package.json

#

thanks for helping me tho

vestal crest
magic phoenix
#

that's exactly the time

#

where I had the most problems

vestal crest
#

Well there you go

magic phoenix
#

you sure that's it

vestal crest
#

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

magic phoenix
#

what alternatives can I try for nextjs

#

maybe vercel is the problem

#

vercel alternatives sorry

vestal crest
#

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.

past wren
#

sitting duck

vestal crest
#

we just have to wait until npm is back up

past wren
#

can you help me with my problem?

magic phoenix
#

ok

vestal crest