“Error authenticating with GitHub” “Problem completing OAuth login”

Hello Railway Support,

I’m having trouble connecting a private GitHub repository to a Railway project.

When I try to connect the repository, I receive the following error:

“Error authenticating with GitHub”

“Problem completing OAuth login”

Repository details:

Repository URL: https://github.com/kimochi-red/kimochi-red

Repository: kimochi-red/kimochi-red

Visibility: Private

Railway project: kimochi-red

Project ID: 0ee1ac88-29b0-40ff-9f86-75167a946266

Environment: production

Current paid Railway account: openkabbalah@gmail.com

Important context:

This same repository, kimochi-red/kimochi-red, was previously used and connected to another Railway account. That previous Railway account has already been deleted.

I’m now trying to connect this repository to my current paid Railway account, openkabbalah@gmail.com, but the OAuth authentication keeps failing.

I have already tried the standard troubleshooting steps, including:

  • Revoking the Railway GitHub OAuth application completely from GitHub
  • Clearing browser sessions, cache, and cookies
  • Trying from a fresh browser session
  • Switching GitHub permissions between “All repositories” and “Only select repositories”
  • Re-authorizing the Railway app in GitHub
  • Making sure I have full access to the private repository
  • Testing the repository as both private and public
  • Disconnecting and reconnecting the GitHub integration

Despite all of this, the same OAuth error persists.

Could there be a conflict because this repository was previously linked to another Railway account that has since been deleted? Is there any internal Railway-side association, installation, or stale OAuth link that needs to be manually removed or reset?

Please help me fully unlink or reset the GitHub/Railway connection for this repository so I can connect it to my current paid Railway account.

Additional issue:

When opening the Railway support form, I’m asked to select a Service related to this request. However, the project/service I need help with does not appear in the dropdown list.

The project I need support for is:

Project: kimochi-red

Project ID: 0ee1ac88-29b0-40ff-9f86-75167a946266

Since kimochi-red is not available as an option in the Service selector, I had to choose:

“N/A (This is unrelated to a Railway service)”

This request is definitely related to that Railway project, but I cannot select it because it does not appear in the list. I’m attaching a screenshot showing the issue.

Thank you.

$10 Bounty

1 Replies

Status changed to Awaiting Railway Response Railway 13 days ago


Railway
BOT

12 days ago

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

Status changed to Open Railway 12 days ago


kpm1725
FREE

10 days ago

The OAuth conflict from a deleted account is a known Railway issue. When a GitHub app installation is tied to an account that gets deleted, Railway doesn't always clean up the installation record on their end, which leaves a stale link that blocks re-authorization. Your diagnosis is correct.

The "service not appearing in dropdown" is likely because the Railway project exists but has no deployed service yet (since you can't connect the repo), so there's nothing for the dropdown to list.

Ask Railway support to manually clear the GitHub App installation record associated with the repository kimochi-red/kimochi-red and any OAuth tokens linked to the deleted account. Once that's purged server-side, your re-authorization should go through cleanly.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...