GitHub integration repository access returns Not Authorized, existing trigger works but new triggers cannot be created
dongjiongwu-cloud
FREEOP

6 days ago

Hello Railway Support,

I am experiencing a GitHub integration issue in my Railway account.

Affected private repositories:

  • dongjiongwu-cloud/dabs
  • dongjiongwu-cloud/context-os

Issue:

Railway backend repository-access and branch-listing checks return “Not Authorized” for both repositories.

Impact:

  • An existing GitHub deployment trigger for context-os continues to work:
    • repository: dongjiongwu-cloud/context-os
    • branch: main
  • However, I cannot create a new GitHub deployment trigger for:
    • repository: dongjiongwu-cloud/dabs
    • branch: release/dabs-developer-v0.1

The DABS repository and release branch are valid and accessible from GitHub.

Troubleshooting already completed:

  1. Verified Railway GitHub App installation and selected-repository access.
  2. Confirmed both repositories are included.
  3. Disconnected and reconnected the Railway GitHub integration.
  4. Confirmed the Railway account is linked to the intended GitHub account.
  5. Confirmed the issue affects backend repo-access queries for both repositories.

Could you please investigate and refresh or repair the GitHub provider repository-access state for this account?

I can provide provider identifiers and backend trace IDs privately upon request.

Thank you.

$10 Bounty

2 Replies

Railway
BOT

6 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 6 days ago


6 days ago

Click Add Service on your project UI, select "Github Repo" and click the Refresh button, This should refresh the Github Repos cache

Screenshot_2026-09-01-15-36-10-84_40deb401b9ffe8e1df2f1cc5ba480b12.jpg

Attachments


dongjiongwu-cloud
FREEOP

3 hours ago

Thank you so much! The problem is solved.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...