Resource not accessible by integration
mustafabugraavci
PROOP

2 months ago

Railway Can't access to github repo. Pushes didn't trigger builds

Solved

10 Replies

Railway
BOT

2 months ago

Make sure you have given the Railway App bot access to your repositories: GitHub Settings -> Applications -> Railway App -> Configure -> Repository access. Then go into your Railway account and unlink and relink the GitHub integration.


Status changed to Awaiting User Response Railway • about 2 months ago


mustafabugraavci
PROOP

2 months ago

image.png

Attachments


Status changed to Awaiting Railway Response Railway • about 2 months ago


Anonymous
PRO

2 months ago

Same


Status changed to Awaiting User Response Railway • about 2 months ago


mustafabugraavci

![image.png](https://station-server.railway.com/attachments/att_01m07zg0jmeh5amrhvnk6n9n0p)

2 months ago

Try disconnect and reconnect the Github Repo in your service settings


Status changed to Awaiting Railway Response Railway • about 2 months ago


Status changed to Awaiting User Response Railway • about 2 months ago


mustafabugraavci
PROOP

2 months ago

tried but same again


Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

2 months ago

Your GitHub App permissions look correct. Since the service-level repo disconnect/reconnect didn't help, try going to your Railway account page and unlinking the GitHub integration entirely, then relinking it (this is different from the service-level repo reconnect). If that still doesn't resolve it, check for any pending permission updates on the Railway GitHub App in your GitHub settings, and as a last resort try uninstalling and reinstalling the Railway GitHub App entirely. In the meantime, you can deploy the latest commit via the Command Palette (CMD/Ctrl + K, then select "Deploy Latest Commit").


Status changed to Awaiting User Response Railway • about 2 months ago


mustafabugraavci
PROOP

2 months ago

image.png

push problem is fixed but this

Attachments


Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

2 months ago

The ##FORBIDDEN## repository forbidden error means Railway's integration token can't access the repo content to clone it, even though pushes are triggering correctly now. Go to GitHub Settings -> Applications -> Railway App and check for any pending permission update requests, then accept them. If that doesn't clear it, fully uninstall the Railway GitHub App from GitHub (GitHub Settings -> Applications -> Railway App -> Uninstall), then reinstall it from this link, granting access to your repositories again, and finally reconnect the repo in your service settings.


Status changed to Awaiting User Response Railway • about 2 months ago



brody

https://www.githubstatus.com/

mustafabugraavci
PROOP

2 months ago

thanks


Status changed to Awaiting Railway Response Railway • about 2 months ago


Status changed to Solved Railway • about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...