17 days ago
Hi — I renamed a GitHub repo and my Railway project's GitHub connection has been broken since. Both prod and staging environments show "GitHub Repo not found" in Settings → Source, even though:
▎ - The Railway GitHub App has been uninstalled + reinstalled fresh
▎ - The App has selected Repository Access
▎ - Reconnecting the source repo in Railway doesn't fix it
3 Replies
17 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 17 days ago
17 days ago
A repo rename can leave Railway’s service source pointing at the old owner/repo slug. GitHub redirects normal git clone/fetch/push traffic after a rename, but Railway’s GitHub App/API/source mapping can still show “GitHub Repo not found” if the service source or repo-list cache is stale.
Things to try in order:
-
In Railway, go to the project canvas and click:
Add -> GitHub Repository -> Refresh
Railway documents this as the forced repo cache refresh step for GitHub source/autodeploy issues.
-
After the repo appears, reconnect the service source to the new owner/new-repo slug in each affected environment/service, then apply/deploy the staged changes. Railway service source config is stored on the service, so prod and staging may both need updating.
-
In GitHub, if the repo is under an org, have an org owner verify:
Organization Settings -> GitHub Apps -> Railway -> Configure
The renamed repo must be selected/approved there. Repository admin rights are not always enough for org app approval.
-
If the picker still shows the old repo or “GitHub Repo not found” after Refresh, this is probably a stale Railway-side GitHub installation/repository cache or stale source reference. At that point Railway support needs to clear/resync the connected GitHub source for the affected project/service/environments.
Useful workaround:
Create a new Railway service from the renamed repo. If that works, the GitHub App permission is fine and the broken piece is the old service’s source mapping. Then copy variables/build settings/domains over or ask Railway to repair the existing source pointer.
10 days ago
I get the error: "Problem processing request with my connected github". I have had my github connected for months and this is the first time I see this issue. I re-authenticated github connection in Railway and reconnected my github repo. But that did not solve the issue.
