NextJS turborepo
Anonymous
TRIALOP

2 years 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.

29 Replies

Anonymous
TRIALOP

2 years ago

1fa2ba21-add1-4880-9d28-b569b2ff6470


Anonymous
TRIALOP

2 years ago

if i run
railway run pnpm build
railway run pnpm start

it works locally


Anonymous
TRIALOP

2 years 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
TRIALOP

2 years ago

site:start: ✓ Ready in 400ms

container event container died

 ELIFECYCLE  Command failed.

site:start:  ELIFECYCLE  Command failed.

ERROR run failed: command exited (1)


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.


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


2 years ago

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


Anonymous
TRIALOP

2 years ago

yes in the root of the project


Anonymous
TRIALOP

2 years ago

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


2 years ago

please send your deployment logs -


Anonymous
TRIALOP

2 years ago


Anonymous
TRIALOP

2 years ago

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


2 years ago

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


Anonymous
TRIALOP

2 years ago

thats my problem there is no error but im getting:

1258243853258064000


2 years ago

can you try setting a HOSTNAME variable to 0.0.0.0


Anonymous
TRIALOP

2 years ago

still the same unfortunately


2 years ago

deployment logs please


Anonymous
TRIALOP

2 years ago


2 years ago

send your next.config.js file


Anonymous
TRIALOP

2 years 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,
},
};

module.exports = withPayload(nextConfig);


2 years ago

can you add -H 0.0.0.0 into your start command


Anonymous
TRIALOP

2 years ago

so should be = "start": "next start -H 0.0.0.0 --port ${PORT-3000}", ?


Anonymous
TRIALOP

2 years ago


Anonymous
TRIALOP

2 years ago

still no luck


2 years ago

show me your public networking section of the settings


Anonymous
TRIALOP

2 years ago

its just started working

1258261210625736700


Anonymous
TRIALOP

2 years ago

that last change might have been it, just might have needed time to update


Anonymous
TRIALOP

2 years ago

Thank you!!!!


2 years ago

no problem!


Loading...