Description

I’m experiencing a persistent GitHub source connection issue with Railway.

The repository is visible and selectable when creating a new Railway project from GitHub. Railway successfully builds and deploys the application from that repository, and the deployed service works correctly.

However, immediately after deployment, the service’s Settings → Source section shows:

“GitHub Repo not found”

The source connection appears to be lost even though the initial deployment was successfully created from that same repository.

When I click Connect Repo and search for the repository again, Railway reports:

“No repositories found — try a different search”

##Repo details:

GitHub repository:

https://github.com/atrx07/aveline-bot

owner: atrx07

default branch: main

visibility: public

already tried-

• Disconnected and reconnected the repository source.
• Refreshed the available repository list.
• Uninstalled and reinstalled the Railway GitHub App.
• Confirmed the Railway GitHub App has access to the repository.
• Confirmed the correct GitHub account owns the repository.
• Created an entirely new Railway project.
• Confirmed the repository is still visible in the initial “New Project → Deploy from GitHub” window.
• Confirmed the same issue occurs again after the first deployment.

additional-

The repository is consistently visible during initial project creation, so Railway clearly has access to it at that stage.

The problem appears specifically after the service has been created: the persisted source association becomes unavailable or points to an invalid GitHub installation/reference.

The application itself deploys and runs successfully. The only broken part is the retained GitHub source connection and therefore automatic deployments.