GitHub Authorization Issue - Cannot See Any Repositories After Re-authorization
wuhaoruisxdx
HOBBYOP

3 months ago

I'm experiencing a critical issue with GitHub integration after re-authorizing my account.

Problem:

  • Before: My GitHub account was properly connected, and the swiv service was deploying successfully from the wuhaoruisxdx/swiv repository (main branch)
  • After re-authorization: I can no longer see ANY repositories in Railway, even though the authorization appears to be complete
  • The error message when trying to select a branch is: "Connected branch does not exist"

What I've tried:

  1. Revoked Railway from GitHub OAuth Apps and reinstalled
  2. Uninstalled Railway from GitHub Apps and re-authorized
  3. Tried selecting "All repositories" during authorization
  4. Cleared browser cache and tried in incognito mode
  5. Confirmed the repository is private and the default branch is main

Current Status:

  • GitHub account: wuhaoruisxdx
  • Repository: wuhaoruisxdx/swiv (private)
  • Default branch: main
  • Railway can no longer see any repositories after re-authorization

Expected Behavior: After re-authorization, I should be able to see my repositories and select the main branch to deploy.

Could you help me resolve this GitHub integration issue? This is blocking my deployments.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway 3 months ago


sam-a
EMPLOYEE

2 months ago

Hello,

Can you make sure you have given the Railway App bot access to your repositories?

GitHub Settings -> Applications -> Railway App -> Configure -> Repository access

Then please go into your Railway account and unlink and relink the GitHub integration.

Best,

The Railway Team


Status changed to Awaiting User Response Railway 2 months ago


Railway
BOT

2 months ago

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!


Railway
BOT

2 months 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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...