Existing worker cannot reconnect to transferred GitHub repo
kas94es4-create
HOBBYOP

a month ago

Subject: Existing service cannot reconnect to transferred GitHub repository

Hello. I need help restoring the GitHub source connection for an existing Railway service without replacing the service or its persistent volume.

Railway project: pleasing-forgiveness

Project ID: f5932726-3108-47cf-8882-2e6f7ef05e9a

Environment: production

Environment ID: ff27e694-e468-4d0d-af29-1416f9394646

Service: worker

Service ID: 2fe25e49-bbf9-4a9b-85ce-0837d6f419c6

The service is still configured with the old GitHub source: kas94es4-create/telegram-npc-game branch: main

The repository is now: Dedher2/telegram-npc-game branch: main

The Railway account has already been reconnected to GitHub as Dedher2, and the Railway GitHub App has been installed on the Dedher2 account with explicit access to Dedher2/telegram-npc-game.

However:

Service Settings → Connect Repo still shows “No repositories found”.

Reinstalling/reconfiguring the Railway GitHub App did not fix it.

The Railway account integration shows Connected as Dedher2.

Deploy latest commit does not fetch the new repository and redirects to the old service deployments.

New commits pushed to the new repository do not trigger a deployment.

A normal Redeploy keeps using the old source snapshot.

Current active deployment ID: 7ce7a6b6-2919-414d-a225-150d8a82c7eb

It is still running old commit: 4a90ddd8fa9f2a199de91aa45e7fa8a0a5a9faac

Current GitHub main is: 15244d04cd526278c2e694c1459faef7104b9f54

Please reconnect the existing worker service to: Dedher2/telegram-npc-game, branch main

Please do not create or replace the service.

The existing service has a persistent Railway volume mounted at /data, environment variables, domain, and production state that must be preserved.

Volume mount: /data

Start command: python railway_service.py

One replica is intentional.

We currently have TELEGRAM_LIVE_DISPATCH=0, so the worker is intentionally operating in SHADOW/safe mode.

Could you repair/update the GitHub source association for this existing service so that it can deploy the latest commit from Dedher2/telegram-npc-game?

Solved

2 Replies

Railway
BOT

a month ago

The service source is still set to kas94es4-create/telegram-npc-game, which no longer exists at that path after the transfer. You can update it to the new repo without replacing the service, its volume, or its variables by running this via the Railway CLI: railway service source connect --repo Dedher2/telegram-npc-game --branch main --service worker (link the project first with railway link if you haven't already). Once the source is updated, push a commit or redeploy to pick up the latest code.


Railway
BOT

a month ago

The service source is still set to kas94es4-create/telegram-npc-game, which no longer exists at that path after the transfer. You can update it to the new repo without replacing the service, its volume, or its variables by running this via the Railway CLI: railway service source connect --repo Dedher2/telegram-npc-game --branch main --service worker (link the project first with railway link if you haven't already). Once the source is updated, push a commit or redeploy to pick up the latest code.


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


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...