I have just moved from vercel to railway. So i deployed the nextjs project from github. The build went successful, after that i generated the public url but the public url is not getting opened even though the project is successfully deployed. Please resolve my issue as soon as possible as I have daily 500-1k visitors in my site.

Here are the variables i have added..i am also sharing deploy and build logs

8 Railway Provided Variables available

AWS_ACCESS_KEY_ID

*******

AWS_DEFAULT_REGION

*******

AWS_SECRET_ACCESS_KEY

*******

GOOGLE_CLIENT_ID

*******

GOOGLE_CLIENT_SECRET

*******

MONGODB_URI

*******

NEXTAUTH_SECRET

*******

NEXTAUTH_URL

*******

RAZORPAY_KEY_ID

*******

RAZORPAY_KEY_SECRET

*******

S3_BUCKET_NAME

33 sec

[stage-0 9/10] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile

[stage-0 9/10] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile 86 ms

[stage-0 10/10] COPY . /app

[stage-0 10/10] COPY . /app 23 ms

exporting to docker image format

exporting to image

importing to docker

[auth] sharing credentials for production-asia-southeast1-eqsg3a.railway-registry.com

[auth] sharing credentials for production-asia-southeast1-eqsg3a.railway-registry.com 0 ms

importing to docker 38 sec

=== Successfully Built! ===

Run:

docker run -it production-asia-southeast1-eqsg3a.railway-registry.com/ee3ceb11-b6d6-4194-ba73-9b411776d98e:08e44a29-658b-4df6-9375-622b59f20d93

Build time: 144.59 seconds

Starting Container

npm warn config production Use --omit=dev instead.

> studylexus@0.1.0 start

> next start -p $PORT -H 0.0.0.0

▲ Next.js 15.3.1

- Local: http://localhost:8080

- Network: http://0.0.0.0:8080

✓ Starting...

✓ Ready in 481ms

[API s3-presigned-url] MODULE LOADED. Initializing...

[API s3-presigned-url] ENV AWS_DEFAULT_REGION: SET (ends with th-1)

[API s3-presigned-url] ENV S3_BUCKET_NAME: SET (studylexus)

[API s3-presigned-url] ENV AWS_ACCESS_KEY_ID: SET (ends with YGEV)

[API s3-presigned-url] ENV AWS_SECRET_ACCESS_KEY: SET (exists)

[API s3-presigned-url] S3 Client INSTANCE CREATED successfully.

(node:15) NOTE: The AWS SDK for JavaScript (v2) is in maintenance mode.

SDK releases are limited to address critical bug fixes and security issues only.

Please migrate your code to use AWS SDK for JavaScript (v3).

For more information, check the blog post at https://a.co/cUPnyil

(Use node --trace-warnings ... to show where the warning was created)

npm error path /app

npm error command failed

npm error signal SIGTERM

npm error command sh -c next start -p $PORT -H 0.0.0.0

npm error A complete log of this run can be found in: /root/.npm/_logs/2025-08-19T11_19_37_816Z-debug-0.log

npm warn config production Use --omit=dev instead.

> studylexus@0.1.0 start

> next start -p $PORT -H 0.0.0.0

▲ Next.js 15.3.1

- Local: http://localhost:8080

- Network: http://0.0.0.0:8080

✓ Starting...

✓ Ready in 582ms

[API s3-presigned-url] MODULE LOADED. Initializing...

[API s3-presigned-url] ENV AWS_DEFAULT_REGION: SET (ends with th-1)

[API s3-presigned-url] ENV S3_BUCKET_NAME: SET (studylexus)

[API s3-presigned-url] ENV AWS_ACCESS_KEY_ID: SET (ends with YGEV)

[API s3-presigned-url] ENV AWS_SECRET_ACCESS_KEY: SET (exists)

[API s3-presigned-url] S3 Client INSTANCE CREATED successfully.

(node:15) NOTE: The AWS SDK for JavaScript (v2) is in maintenance mode.

SDK releases are limited to address critical bug fixes and security issues only.

Please migrate your code to use AWS SDK for JavaScript (v3).

For more information, check the blog post at https://a.co/cUPnyil

(Use node --trace-warnings ... to show where the warning was created)