Skip to content
GitHub App has repository access but Railway cannot load branches after incident recovery
ikennaegwim
OP

24 days ago

I am recovering a production project following the October 21 incident.

The Railway GitHub App is installed and explicitly has access to the private repository, and the existing service source binding is still present.

However, Railway continued to show:

Could not load branches. Retry

A scheduled build also failed with an error saying that the Railway project did not have access to the connected GitHub repository.

Troubleshooting already completed included:

  • confirming the Railway GitHub App has access to the repository;
  • unsuspending the existing App installation;
  • confirming repository scope and permissions;
  • waiting and refreshing the service Source page;
  • using the Source-page Retry action;
  • refreshing repository discovery from the project canvas;
  • confirming no new code was pushed and no unexpected deployment occurred.

I deliberately avoided disconnecting individual service source bindings or reinstalling the GitHub App because this is a production recovery and I wanted to avoid an unintended deployment.

Could Railway confirm the safest supported way to refresh the GitHub authorization without changing existing service bindings or triggering a deployment?

Update / resolution: Railway confirmed that, following the October 21 incident response, both the GitHub App installation and the account-level GitHub authorization may need to be renewed.

The supported recovery was to reconnect GitHub from Railway Account Settings, confirm the Railway GitHub App still had repository access, and then verify repository/branch discovery.

Renewing the account-level GitHub authorization restored repository discovery in my case without changing the running production deployments.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

During the October 21 incident response, GitHub connections and OAuth tokens were revoked, so a Railway GitHub App that still has access to the repository is only part of the fix. The account-level GitHub authorization also has to be renewed. In a team project, the member who originally connected the repository is the one who needs to do this.

The supported order is: reconnect GitHub in your Account Settings first, confirm the Railway GitHub App still has access to IkennaEgwim/Finsensa (your screenshot shows it does), then disconnect and reconnect the repository in the service's Settings. Uninstalling and reinstalling the GitHub App is optional. It is a precaution if you want the app issued fresh credentials, not a required step.

Your running deployments keep serving their last successful deployment. Commits pushed while deploys were paused do not deploy on their own, and a new build starts when you choose Deploy Latest Commit or push a commit. Because the service has "Auto deploys when pushed to GitHub" turned on, you can disable that toggle before reconnecting if you want full control over when the next build runs, then deploy deliberately once branches load again.


Status changed to Awaiting User Response dizzydes90 • 24 days ago


Railway
BOT

16 days 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 • 16 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...