21 days ago
Problem: Deploys triggered "from source" (CI's railway redeploy --from-source and the dashboard) stopped picking up new commits — the service kept silently redeploying an old commit even after several new pushes, with no error. Trying to reconnect the source now fails outright with: "No project member has access to this GitHub repository. Check if the GitHub Railway App is installed and project members have their GitHub accounts connected."
Already tried:
- Confirmed the repo is visible from the GitHub account linked to my Railway account (tkosman)
- Disconnected/reconnected my GitHub account in Railway, explicitly authenticating as tkosman (repo owner) rather than a second GitHub account I also use — error persisted
- Fully uninstalled the Railway GitHub App from github.com/settings/installations and reinstalled fresh with explicit access to tkosman/zerwomierz — error persisted
- Reproduced the same failure via CLI (service source connect, redeploy --from-source) — opaque errors despite railway status --json correctly showing source.repo: tkosman/zerwomierz
- Confirmed the service itself is healthy — plain railway redeploy (no --from-source) succeeds
This points to a stuck/corrupted backend record for this service's source-repo linkage, since a full GitHub App uninstall+reinstall didn't clear it.
You can see how repo is being configured even though auto deploy is unavailable (cannot access private repo).
How to fix that?
Attachments
2 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
20 days ago
Tracked this down, and your instinct was right, it was a stuck record on our side, not anything wrong with your GitHub.
When you uninstalled the Railway GitHub App, that deleted the old installation. But our cached link for tkosman/zerwomierz kept pointing at that dead installation, so every access check failed to get a token for it and concluded no project member could reach the repo. That's the "No project member has access" error, and it's why reinstalling and reconnecting your account didn't clear it. The old pointer just never got overwritten.
I've refreshed that record to point at your current installation and confirmed we can read the repo again. Your reconnect attempts left the service with no source connected, so the last step is on you: reconnect tkosman/zerwomierz in the service's Source settings (or railway service connect), then enable auto deploy. It'll stick this time, and --from-source will pick up new commits again.
Let me know if anything's still off.
Railway Team
Status changed to Awaiting User Response Railway • 20 days ago
Status changed to Solved sam-a • 20 days ago
sam-a
Tracked this down, and your instinct was right, it was a stuck record on our side, not anything wrong with your GitHub. When you uninstalled the Railway GitHub App, that deleted the old installation. But our cached link for `tkosman/zerwomierz` kept pointing at that dead installation, so every access check failed to get a token for it and concluded no project member could reach the repo. That's the "No project member has access" error, and it's why reinstalling and reconnecting your account didn't clear it. The old pointer just never got overwritten. I've refreshed that record to point at your current installation and confirmed we can read the repo again. Your reconnect attempts left the service with no source connected, so the last step is on you: reconnect `tkosman/zerwomierz` in the service's Source settings (or `railway service connect`), then enable auto deploy. It'll stick this time, and `--from-source` will pick up new commits again. Let me know if anything's still off. Railway Team
20 days ago
I can confirm that everything works now. Thank you for the support!
Status changed to Awaiting Railway Response Railway • 20 days ago
Status changed to Solved tkosman4development • 20 days ago