a month ago
I am trying to stage the first deployment of a private GitHub repository through Railway Infrastructure as Code. Railway recognizes and resolves the repository in the service Source settings, but the staged-change banner still says:
"No GitHub installation found for repo: Girthquakess/Daylight-Cabin-The-Entity"
Project: Daylight Cabin - The Entity
Project ID: c9ffd349-b7fb-498f-9b48-b22dafe287a1
Environment: production
Environment ID: 5bd9b49e-0e75-4ae3-9f10-ccee78be2283
Service: The Entity
Service ID: c33b46c0-1804-4704-8b78-2cb0b6762de5
Repository: https://github.com/Girthquakess/Daylight-Cabin-The-Entity (private)
Branch: main
Plan: Trial
What I verified:
- Railway's GitHub account integration is connected as Girthquakess.
- GitHub shows the Railway App installed on August 23, 2026 and scoped only to this repository.
- The repository appears in Railway's picker, and the service Source section resolves the repository and main branch.
- Automatic deployments are disabled.
- No build or deployment has been attempted yet, so there are no deployment logs.
Troubleshooting already completed:
- Reconnected Railway's GitHub account integration.
- Refreshed Railway's repository cache twice.
- Disconnected and reconnected the service to the same repository and main branch.
- Reloaded the dashboard and allowed time for propagation.
- Created a brand-new staged-only service with the same repository and branch. It immediately showed the same warning, so that undeployed diagnostic service was discarded.
Current state:
- The original service and persistent volume remain staged.
- No deployment, cloud Discord connection, token exposure, or data migration occurred.
- The warning blocks a safe first deployment.
Could Railway please refresh or inspect the backend GitHub App installation mapping for this project/workspace, or explain why the dashboard resolves the repository while staged IaC does not?
1 Replies
a month ago
The staged changes on your service failed to apply with the "No GitHub installation found" error, which means Railway's backend cannot resolve the GitHub App installation for that repository even though the repo picker sees it. Since you've already reconnected the account integration and refreshed the cache without effect, the next step from our troubleshooting guide is to fully uninstall the Railway GitHub App from your GitHub account at https://github.com/settings/installations (not just reconnect the Railway integration), wait a minute, then reinstall it at https://github.com/apps/railway-app/installations/new, scoping it to the same repository. After reinstalling, discard your current staged changes, reconnect the service to the repo, and apply the changes again.
Status changed to Awaiting User Response Railway • about 1 month ago
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