Skip to content
All new deployments from GitHub repo fails before the build step (Railpack Python 13)
demidost
OP

23 days ago

All new deployments fails.

The Log response is:

"This project doesn't have access to . A member of the project must be a collaborator on the repository. Reconnect the GitHub repository under Service Settings → Source, or reinstall the Railway GitHub App and grant it access to this repo."

The thing is the project DO HAVE access to my GitHub and always had.

Did anyone experience similar issues recently? Is it related to the recent incident?

Solved

6 Replies

Status changed to Awaiting Railway Response Railway • 23 days ago


vstavskyi

23 days ago

Got error Failed to build an image

load metadata for docker.io/library/python:3.11-slim

load metadata for docker.io/library/node:24-alpine

Hit:1 http://deb.debian.org/debian trixie InRelease

The following additional packages will be installed:

python3.13-minimal


Status changed to Awaiting Railway Response Railway • 23 days ago


Status changed to Awaiting User Response Railway • 23 days ago


nickvanzdev

21 days ago

i am experiencing the same issue all of the sudden. very weird.

This project doesn't have access to ..... A member of the project must be a collaborator on the repository. Reconnect the GitHub repository under Service Settings → Source, or reinstall the Railway GitHub App and grant it access to this repo.


Status changed to Awaiting Railway Response Railway • 21 days ago


Status changed to Awaiting User Response Railway • 21 days ago


nickvanzdev

19 days ago

Is there any progress?? Please anyone?? I am still unable to deploy anything to my production environment @railway


Status changed to Awaiting Railway Response Railway • 19 days ago


Status changed to Awaiting User Response Railway • 19 days ago


demidost
OP

18 days ago

No progress at all. Reconnection under Service Settings → Source doesn't fix the issue.


Status changed to Awaiting Railway Response Railway • 18 days ago


dizzydes90
EMPLOYEE

18 days ago

We're sorry this is blocking your production deploys. Reconnecting the repository under Service Settings → Source on its own isn't enough here. During the October 21 incident, GitHub connections were revoked, so the account-level link and the GitHub App's repository access usually need to be redone first.

Please reconnect GitHub in your account settings, then in GitHub open Settings, Applications, Railway App, Configure, and make sure Repository access includes this repository. After that, disconnect and reconnect the repository in the service's Source settings, and run Deploy Latest Commit from the command palette (Cmd+K, or Ctrl+K on Windows). In a team project, the member who originally connected the repository has to do these steps.

If a fresh deploy still fails after all of that, please share the deployment ID and the exact error from that deployment so we can look at your project directly.


Status changed to Awaiting User Response Railway • 18 days ago


demidost
OP

18 days ago

Ok that worked.

A quick recap:

go to the link from previous message (ACCOUNT Settings) and scroll down to "Account Integrations" sections. Click "Connect" button for GitHub Card.

Then go to your PROJECT's settings. Check that "Auto deploys when pushed to GitHub" is Enabled.


Status changed to Awaiting Railway Response Railway • 18 days ago


Status changed to Solved Railway • 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...