Railway service stuck on old Root Directory config after repo change - "Could not find root directory: worker"
andi586
HOBBYOP

a month ago

Hi Railway Support,

I'm having issues with my Worker service deployment.

Problem 1:

When I connect my GitHub repo (andi586/worker) to a Railway service,

I get "Could not find root directory: worker" error even though I've

cleared the Root Directory field.

Problem 2:

When trying to reconnect the repo, I get "Failed to get private networks" error.

My setup:

- Project: scriptflow-video-merge

- Service: scriptflow-poc

- GitHub repo: andi586/worker

- Branch: main

- index.js is in the ROOT of the repo (not in a subdirectory)

- Start command: node index.js

What I've tried:

- Clearing the Root Directory field

- Reconnecting the GitHub repo multiple times

- railway up from CLI (uploads but shows old commit hash)

Questions:

1. Why is Railway still looking for a "worker" directory when Root Directory is empty?

2. What does "Failed to get private networks" mean?

3. How do I properly connect a new GitHub repo to an existing service?

Thank you

$10 Bounty

2 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved andi586 about 1 month ago


andi586
HOBBYOP

a month ago

Sorry, I accidentally marked this as solved. The issue is not resolved yet. Please reopen.


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Open Railway about 1 month ago


You might have railway.toml or railway.json file, that sets the root directory? If not, try making a new service from your github repo.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...