a month ago
Project: discerning-comfort
Service: backend
I'm unable to connect my service to my GitHub repository. "Settings → Source → Connect Repo" shows "No repositories found - try a different search" no matter what I do.
What's already confirmed correct on my end:
- GitHub account (Jager2026) is correctly connected at the Railway account level (Account Settings → Account Integrations → GitHub → "Connected as Jager2026")
- The Railway GitHub App is installed on the Jager2026 account with "Only select repositories" access, and the specific repository (Jager2026/hospitality-financial-os) is confirmed selected in the app's permission settings
- I've tried: disconnecting and reconnecting the service's Source multiple times, uninstalling and reinstalling the GitHub App, hard refreshes, and logging out/back in via GitHub specifically as Jager2026
- None of this has surfaced the repository in Connect Repo
Could someone please check server-side whether there's a stale GitHub App installation/repo linkage for this service that needs to be manually cleared? This matches a pattern I found reported by another user with the same symptom, where support had to clear it manually.
Thank you.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Please try the following steps in order:
-
In Railway, open Project → Add → GitHub Repository instead of using the service's Connect Repo option. Click Refresh first to force Railway to refresh its GitHub repository cache, then search for
Jager2026/hospitality-financial-os. -
If the repository appears, select it and connect it to the existing
backendservice. -
If it still doesn't appear, try connecting it through the Railway CLI:
railway link
railway service source connect --repo Jager2026/hospitality-financial-os --branch main --service backendMake sure main is the actual default branch.
- If the CLI also cannot find/connect the repository, create a temporary Railway project and check whether the repository appears under Add → GitHub Repository.
If it appears in the new project but not discerning-comfort, the problem is likely a stale project/service-level GitHub linkage. If it doesn't appear anywhere, the issue is likely with the Railway GitHub App installation/cache, and Railway support should check the server-side installation/repository mapping.
9 days ago
You’ve already ruled out most of the normal GitHub App setup failures, so I’d separate “the dashboard repository picker is stale” from “Railway’s backend cannot resolve the GitHub installation”.
Railway’s current troubleshooting docs specifically recommend Project Canvas → Add → GitHub Repository → Refresh because that forces a repository-cache refresh rather than simply reopening the existing service’s Connect Repo picker. After doing that, give the cache a few minutes and search for Jager2026/hospitality-financial-os again.
There is also now a documented CLI path that can test the backend independently of the dashboard picker. After authenticating and linking the project/environment, try:
railway service source connect –repo Jager2026/hospitality-financial-os –branch main –service backend
That command is useful diagnostically as well as potentially fixing it.
If the CLI succeeds, the GitHub installation itself is valid and the failure is isolated to the dashboard repository discovery/cache.
If the CLI returns a repository-access, “repo not found”, or “no GitHub installation” type error despite the Railway GitHub App visibly having access to that repository, then this is no longer a browser/cache issue. It means Railway’s backend is not resolving the GitHub App installation/repository mapping correctly.
Railway’s own documented requirements are: at least one project member must have a connected GitHub account with contributor access, the Railway GitHub App must have repository access, and there must be no pending App permission update. You’ve already described satisfying those requirements and reinstalling the App.
At that point I would avoid deleting or recreating the backend service. Preserve the existing variables/domain/service configuration and give Railway support the project ID, service ID, environment, exact repository name, GitHub username, and the exact CLI error from the source-connect command. That gives them a clean reproduction showing whether the failure is only repository discovery or the server-side installation binding itself.
If the CLI connection works, deploy the newly connected source normally and the existing backend service configuration can remain in place.