Railway•6mo ago

bun + turborepo monorepo application failing to respond

For some reason my application is saying it's failing to respond, however it successfully deploys (or at least it says so...) I have PORT configured for Railway's default to be injected, so that isn't the issue. I also setup both my start & build scripts, which are: Start: bun start --filter=api Build: bun run build --filter=api

Solution:

something you are doing is un-setting them

Jump to solution

75 Replies

Percy•6mo ago

Project ID: aac0388c-812d-41d2-abad-f664d8a4fc9f

bereketOP•6mo ago

aac0388c-812d-41d2-abad-f664d8a4fc9f

Brody•6mo ago

make sure you are listening on the $PORT environment variable

bereketOP•6mo ago

server.listen({ host: process.env.HOST, port: process.env.PORT }, (err, address) => {
    if (err) {
      Logger.error("SERVER", err.message);
      process.exit(1);
    }

    Logger.info("SERVER", `Listening at ${address}`);
  });

server.listen({ host: process.env.HOST, port: process.env.PORT }, (err, address) => {
    if (err) {
      Logger.error("SERVER", err.message);
      process.exit(1);
    }

    Logger.info("SERVER", `Listening at ${address}`);
  });

bereketOP•6mo ago

seem to be getting this now, weird

Brody•6mo ago

there is no HOST variable, just use 0.0.0.0

bereketOP•6mo ago

I have it set to (where these are under the env cost)

HOST: z.string().default("0.0.0.0"),
API_URL: z.string().default("http://localhost:8080"),

HOST: z.string().default("0.0.0.0"),
API_URL: z.string().default("http://localhost:8080"),

Sorry, it shouldn't been:

server.listen({ host: env.HOST, port: env.PORT }, (err, address) => {
    if (err) {
      Logger.error("SERVER", err.message);
      process.exit(1);
    }

    Logger.info("SERVER", `Listening at ${address}`);
  });

server.listen({ host: env.HOST, port: env.PORT }, (err, address) => {
    if (err) {
      Logger.error("SERVER", err.message);
      process.exit(1);
    }

    Logger.info("SERVER", `Listening at ${address}`);
  });

Brody•6mo ago

what is PORT set to in zod ?

bereketOP•6mo ago

PORT: z.number().default(8080),
HOST: z.string().default("0.0.0.0"),

PORT: z.number().default(8080),
HOST: z.string().default("0.0.0.0"),

Brody•6mo ago

you should use process.env.PORT instead, and if that isn't available then you can default to 8080, not sure what that looks like in zod though

bereketOP•6mo ago

will try rn but i doubt thats the issue since it should be defined

Brody•6mo ago

is it? do you have a PORT service variable? you'd still want to be listening on the PORT environment variable in code though

bereketOP•6mo ago

running into this issue now when i try to deploy those new changes (but anything really)

bereketOP•6mo ago

keeps retrying

Brody•6mo ago

would you happen to have a custom start command set now?

bereketOP•6mo ago

the structure of my codebase is:

apps
-> api
package.json

apps
-> api
package.json

Brody•6mo ago

do you have the new builder also enabled? the new builder has a bug where it doesn't pass in the start command correctly

bereketOP•6mo ago

nope i dont misread my bad

bereketOP•6mo ago

Brody•6mo ago

hmmm well those logs are not helpful, bun never prints anything helpful it seems I assume you can still run the same pair of build and start commands locally without issues?

bereketOP•6mo ago

yeah it all works locally same start & build commands

Brody•6mo ago

even if you deleted the project and did another clone?

bereketOP•6mo ago

on railway or git

Brody•6mo ago

on git, delete the project locally and clone it again what version of bun do you use locally, and what version of bun is railway using for your project? it's always best to have the cloud platform running the same versions of stuff as you run locally

bereketOP•6mo ago

this is what my package.json looks like:

{
  "name": "test",
  "private": true,
  "scripts": {
    "build": "turbo build",
    "dev": "turbo dev",
    "start": "turbo start",
    "lint": "turbo lint",
    "format": "prettier --write \"**/*.{ts,tsx,md}\""
  },
  "devDependencies": {
    "prettier": "^3.3.0",
    "turbo": "latest"
  },
  "engines": {
    "node": ">=18"
  },
  "packageManager": "[email protected]",
  "workspaces": [
    "apps/*"
  ],
  "dependencies": {
    "tsc-alias": "^1.8.10"
  }
}

{
  "name": "test",
  "private": true,
  "scripts": {
    "build": "turbo build",
    "dev": "turbo dev",
    "start": "turbo start",
    "lint": "turbo lint",
    "format": "prettier --write \"**/*.{ts,tsx,md}\""
  },
  "devDependencies": {
    "prettier": "^3.3.0",
    "turbo": "latest"
  },
  "engines": {
    "node": ">=18"
  },
  "packageManager": "[email protected]",
  "workspaces": [
    "apps/*"
  ],
  "dependencies": {
    "tsc-alias": "^1.8.10"
  }
}

i use [email protected]

Brody•6mo ago

what version does railway use?

bereketOP•6mo ago

where can i check that?

Brody•6mo ago

temporarily change the start command to a command that prints the version of bun

bereketOP•6mo ago

alright

bereketOP•6mo ago

used the railway cli thank god i got a bit more context

Brody•6mo ago

are you on the v2 runtime?

bereketOP•6mo ago

yeah

Brody•6mo ago

also, I the API app not with bun?

bereketOP•6mo ago

wdym

Brody•6mo ago

node dist/index.js

bereketOP•6mo ago

got it up to this point now still getting

Application failed to respond

in the api package, my scripts are:

 "scripts": {
    "dev": "tsx watch --clear-screen=false src/index.ts",
    "migrate": "drizzle-kit generate",
    "build": "tsc -p tsconfig.json && tsc-alias -p tsconfig.json",
    "start": "node dist/index.js"
  },

 "scripts": {
    "dev": "tsx watch --clear-screen=false src/index.ts",
    "migrate": "drizzle-kit generate",
    "build": "tsc -p tsconfig.json && tsc-alias -p tsconfig.json",
    "start": "node dist/index.js"
  },

Brody•6mo ago

we are back to this, please make these changes

bereketOP•6mo ago

oh shoot forgot to change that back what's the port railway uses by default? just curious

Brody•6mo ago

it's random, that's why your app needs to listen on the PORT environment variable please make this change

bereketOP•6mo ago

doing that rn alright just tried with:

  server.listen(
    {
      host: process.env.HOST ?? "0.0.0.0",
      port: process.env.PORT ? Number(process.env.PORT) : 8080,
    },
    (err, address) => {
      if (err) {
        Logger.error("SERVER", err.message);
        process.exit(1);
      }

      Logger.info("SERVER", `Listening at ${address}`);
    }
  );

  server.listen(
    {
      host: process.env.HOST ?? "0.0.0.0",
      port: process.env.PORT ? Number(process.env.PORT) : 8080,
    },
    (err, address) => {
      if (err) {
        Logger.error("SERVER", err.message);
        process.exit(1);
      }

      Logger.info("SERVER", `Listening at ${address}`);
    }
  );

seems to keep using 8080 thought, so PORT must not be defined by railway

bereketOP•6mo ago

wtf am i doing something wrong ok so apparently it works if i just manually add PORT to my env variables thank you

Brody•6mo ago

while that will work, and it's by far the simpler way this is not the recorded way

bereketOP•6mo ago

okay so after a bit of debugging it seems like dotenv just doesnt want to parse the env variable on railway it works locally though, which is weird

Brody•6mo ago

dotenv parses .env files

bereketOP•6mo ago

yeah

Brody•6mo ago

railway does not create .env files they inject the variables directly into the environment

bereketOP•6mo ago

wdym how would process.env not work? i understand this but not this

Brody•6mo ago

I don't know how I could clarify further

bereketOP•6mo ago

well maybe i can explain what i mean

bereketOP•6mo ago

i have variables that i set on railway, like below:

bereketOP•6mo ago

and im accessing them through process.env but when i test it by console logging, like console.log(process.env.GOOGLE_CLIENT_ID ?? "some google client id"), it doesn't work, and goes to the fallback of some google client id

Brody•6mo ago

your code is doing something to unset them

bereketOP•6mo ago

oh actually i think the issue is that the env variables are located in the root directory and not in apps/api

Brody•6mo ago

the environment variables are injected into the containers environment, they aren't scoped to any specific directory in a production environment like railway you don't even need to call dotenv

bereketOP•6mo ago

this is my src/utils/env.ts:

import "dotenv/config";
import { z } from "zod";

export const env = z
  .object({
    DATABASE_URL: z
      .string()
      .default("default db url goes here"),

    // ... other variables
  })
  .parse(process.env);

import "dotenv/config";
import { z } from "zod";

export const env = z
  .object({
    DATABASE_URL: z
      .string()
      .default("default db url goes here"),

    // ... other variables
  })
  .parse(process.env);

bereketOP•6mo ago

I have it set in Railway and in my src/index.ts, all I do is console.log(env.DATABASE_URL) and for some reason it doesn't return the value that I put in railway and instead that fallback of default db url goes here

Brody•6mo ago

can zod even parse process.env

bereketOP•6mo ago

yes

Brody•6mo ago

haha don't say yes, if it could, it would work

bereketOP•6mo ago

have done it before + works locally

Brody•6mo ago

so you have something missconfigured

bereketOP•6mo ago

will try without using zod for it

import "dotenv/config";

export const env = {
  DATABASE_URL: process.env.DATABASE_URL || "postgres://butler:[email protected]:5432/postgres",
  // ... other variables
};

import "dotenv/config";

export const env = {
  DATABASE_URL: process.env.DATABASE_URL || "postgres://butler:[email protected]:5432/postgres",
  // ... other variables
};

doesn't seem to work with this either the thing is it works fine locally so i can't repro it

Solution

Brody•6mo ago

something you are doing is un-setting them

Brody•6mo ago

try removing dotenv because as mentioned, you don't need to call it when on railway

Gaming

Programming

bun + turborepo monorepo application failing to respond