NextJS turborepo

Anonymous

TRIAL

a year ago

Hi I have a turbo monorepo with a Next app I am trying to deploy. The app builds and deploys fine but i cant access the site at the url.

In the logs im not sure if its related but I can see an:

ELIFECYCLE Command failed.

The app works fine on vercel, not sure if i need to make changes to get it to work on railway.

2 Replies

Anonymous

TRIAL

a year ago

1fa2ba21-add1-4880-9d28-b569b2ff6470

Anonymous

TRIAL

a year ago

if i run
railway run pnpm build
railway run pnpm start

it works locally

Anonymous

TRIAL

a year ago

it seems to dectect next server running at port 3000 when i click generate domain but then i get, application failed to respond when i click into it

Anonymous

TRIAL

a year ago

site:start: ✓ Ready in 400ms

container event container died

ELIFECYCLE Command failed.

site:start: ELIFECYCLE Command failed.

ERROR run failed: command exited (1)

marco-quintella

HOBBY

a year ago

Suggest you to follow this template as reference for config

https://github.com/railwayapp-templates/nextjs-prisma/tree/main

Also, remember to set the defined build and start commands on service settings, as usual next deault package comes with different command names.

marco-quintella

HOBBY

a year ago

Pay attention to the start command at the example. The PORT env variable interpolation.

brody

EMPLOYEE

a year ago

are you in the root of the project when you run these commands?

Anonymous

TRIAL

a year ago

yes in the root of the project

Anonymous

TRIAL

a year ago

tried setting next start --port ${PORT-3000} but still no luck

brody

EMPLOYEE

a year ago

please send your deployment logs -

Anonymous

TRIAL

a year ago

1258240822051078164

Anonymous

TRIAL

a year ago

FYI those invalid next config options are not the cause of any issues since they come up when its working

brody

EMPLOYEE

a year ago

I'm not seeing any errors in those logs, what's not working?

Anonymous

TRIAL

a year ago

thats my problem there is no error but im getting:

1258243853258064000

brody

EMPLOYEE

a year ago

can you try setting a HOSTNAME variable to 0.0.0.0

Anonymous

TRIAL

a year ago

still the same unfortunately

brody

EMPLOYEE

a year ago

deployment logs please

Anonymous

TRIAL

a year ago

1258250996694388767

brody

EMPLOYEE

a year ago

send your next.config.js file

Anonymous

TRIAL

a year ago

const { withPayload } = require('@payloadcms/next/withPayload')
/** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: true,
// images: {
// domains: [
// "res.cloudinary.com",
// "images.pexels.com",
// "placeimg.com",
// "placehold.co",
// "via.placeholder.com",
// "nursify.vercel.app",
// ],
// },
images: {
remotePatterns: [
{
protocol: "https",
hostname: "", }, { protocol: "http", hostname: "",
},
],
},
typescript: {
// !! WARN !!
// Dangerously allow production builds to successfully complete even if
// your project has type errors.
// !! WARN !!
ignoreBuildErrors: true,
},
};