Running env in the Console shows only RAILWAY_* built-ins — no DATABASE_URL, no application variables at all.
dev-wvisitacion
FREEOP

a month ago

Service variables are not being injected into the container. All 11 variables are saved and visible in the Raw Editor, but running env in the Console shows only RAILWAY_* built-ins — no DATABASE_URL, no application variables at all. As a result process.env.DATABASE_URL is undefined and the app falls back to 127.0.0.1:5432.

Project: 988796ec-beb8-4ce4-ad3d-ef02785c5005

Service: 81edbc0d-a018-48d2-8894-97774c49c45b (Personae)

Deployment: 10a6f853-e99c-4d43-9cad-72773292e05c

Environment: production

RAILWAY_BETA_ENABLE_RUNTIME_V2=1 is present in the container environment.

Solved

1 Replies

Railway
BOT

a month ago

Your 11 application variables (including DATABASE_URL) are currently staged but have not been applied yet, so the running container was never given them. You should see a deploy bar at the top of the project canvas showing 14 pending changes. Clicking Deploy on that bar will apply the variables and trigger a new deployment that includes them.


Status changed to Awaiting User Response Railway • about 1 month ago


Status changed to Solved dev-wvisitacion • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...