2 months ago
Service: my Railway project (private GitHub repo, personal account — not an organization)
Branch: master
Issue: Every deployment attempt fails during initialization with:
Initialization > Snapshot code
[ERROR] ##FORBIDDEN## repository forbidden
Automatic "Diagnose" also fails ("Diagnosis failed for this deployment").
What I've already tried, in order:
Confirmed the latest commit is correctly detected by Railway (correct commit message/metadata) — so the GitHub webhook connection is receiving push events.
Verified the Railway GitHub App's permissions: full read/write on code, actions, administration, checks, commit statuses, deployments, pull requests, workflows, plus read on metadata.
Repository access set to "All repositories."
App not suspended.
Clicked "Save" on repository-access settings to force GitHub to re-issue access — temporarily fixed an earlier "Resource not accessible by integration" error, after which new commits were detected, but the snapshot/clone step itself still fails.
Fully uninstalled the Railway GitHub App from GitHub, then reconnected via "Connect Repo" — fresh install, repo selectable/selected again.
Hard-refreshed browser, disconnected/reconnected source again.
Confirmed the GitHub account is personal (not an org) — ruling out SAML SSO authorization as the cause.
The error persists identically at "Snapshot code" specifically, which looks like an internal Railway step. Could you check for a stale/cached access token or internal permission record for this service that needs clearing/regenerating?
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We're sorry for the trouble. GitHub is currently experiencing elevated error rates that are affecting auto-deploys, code snapshots, and related operations across Railway. Your "repository forbidden" error at the Snapshot code step is consistent with this, and we can confirm the same class of failure is happening broadly right now, not just on your repository. Your earlier successful deploys today confirm this is intermittent rather than a permissions problem on your end. You can follow updates on the GitHub incident at https://status.railway.com/incident/W4MIGEVT, and once GitHub stabilizes, a new push or manual redeploy should go through normally.
Status changed to Awaiting User Response brody • about 2 months ago
a month 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 1 month ago