19 days ago
Railway GitHub App (install ID 133985458) returns "Bad credentials" specifically for ywl93/gaia-harvest and only this repo. Verified clean on GitHub side: App listed at repo-level installations, "All repositories" set, no webhooks/deploy keys/rulesets/branch-protection conflicts. Two other private repos in the same App install connect to Railway without issue — only gaia-harvest is affected. Reproduces on a fresh service: bbbc3fcc-62e0-47de-bb2c-06553de89008 (also Bad credentials). Existing affected service: 42f979b3-622e-4708-a742-bbad8715a3e2. Project: 8cc4015b-c819-44b6-a607-d10781a91eda. Likely a stale stored GitHub repo identifier on Railway's side for this specific repo. Asking for backend lookup + refresh.
4 Replies
Status changed to Awaiting Railway Response Railway • 19 days ago
17 days ago
We were experiencing a major service disruption (details at https://status.railway.com/incident/I23M92U0) that could have left stale credential state for specific repos. As a first step, could you please go to your Railway account settings, unlink the GitHub integration entirely, then relink it? This forces a full credential refresh on our end and often clears repo-specific staleness. If the issue persists after relinking, let us know and we'll investigate further on the backend.
Status changed to Awaiting User Response Railway • 17 days ago
chandrika
We were experiencing a major service disruption (details at https://status.railway.com/incident/I23M92U0) that could have left stale credential state for specific repos. As a first step, could you please go to your [Railway account settings](https://railway.com/account), unlink the GitHub integration entirely, then relink it? This forces a full credential refresh on our end and often clears repo-specific staleness. If the issue persists after relinking, let us know and we'll investigate further on the backend.
16 days ago
This keeps happening to me too. I tried multiple times unlinking Github and linking it again, and still nothing. Kindly advise a way forward urgently, this is ridiculous.
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
Same here. "Bad credentials" after multiple relinking Github but still nothing works.
14 days ago
Hey all, the "bad credentials" was due to an outage that Github was having and it resolved on the Railway side once GitHub resolved their incident: https://www.githubstatus.com/incidents/k5z4d1v1tqmt
If you're still running into issue though, please let us know and we'll get you sorted!
Status changed to Awaiting User Response Railway • 14 days ago
7 days 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 • 7 days ago