Hi Railway team,

we’re having an issue with GitHub deployments across multiple Railway services in the same project/workspace.

All services connected to the GitHub repository are failing during the “Initialization > Snapshot code” step with:

[ERROR] ##NOT-AUTHORIZED## repository not authorized

In each service settings, under Source, the repo is shown as connected, but the production branch section shows:

Bad credentials

Repository:

delavegaOpengl/betting

What we already tried:

• disconnected and reconnected the repository from the Railway service settings
• uninstalled the Railway GitHub App from GitHub
• reinstalled the Railway GitHub App
• granted Railway access to all repositories
• confirmed the repository is included in the Railway GitHub App installation
• logged out and back into Railway
• retried deployments after reconnecting the repo

The issue still persists across all GitHub-connected services, not just one service.

Could you please check if there is a stale or broken GitHub installation/token mapping on Railway’s side for this workspace/project/repository? It looks like Railway can still display the repository as connected, but cannot authorize the snapshot/clone step.

Affected:

• Repository: delavegaOpengl/betting
• Services affected: all services connected to this GitHub repo
• Error: ##NOT-AUTHORIZED## repository not authorized
• Deployment stage: Initialization > Snapshot code
• Source settings status: Bad credentials

Thanks.