19 days ago
Hi Railway Support Team,
I am experiencing a persistent deployment failure at the snapshot stage due to a GitHub authorization issue, and I've exhausted all standard troubleshooting steps.
[What I Have Tried]
- Verified repository access settings under the GitHub Railway App (changed from "Only select repositories" to "All repositories" and saved).
- Uninstalled the Railway App completely from my GitHub settings, disconnected GitHub inside my Railway Account Settings, and re-authenticated/re-installed everything from scratch.
Railway still uses invalid or cached credentials, resulting in "Bad credentials".
Please help on this case.
Thank you for your help!
Pinned Solution
19 days ago
If SV_2026 is visible in Railway, repo visibility is probably not the issue anymore.
Since only sv-frontend and sv-backend fail while the other services deploy, I’d treat it as stale source config on those two services. For each failing service: Settings -> Source -> disconnect the repo, save, then connect the repo/branch again from that service. After that, trigger Deploy latest commit, not just retry the old failed deploy.
Also check if those two services still point to an old repo id or old branch name from before the GitHub app reinstall. Seeing the repo in the picker doesnt always mean the old service source token got refreshed.
3 Replies
19 days ago
Your other services in this project (chen_eating_backend, huahan_backend, huahan_frontend) have recent successful deployments, so your GitHub App installation and account-level connection are working. The "Bad credentials" error is isolated to sv-frontend and sv-backend. Try disconnecting the GitHub repo from those specific services in each service's Settings tab, then reconnecting it. You can also force a credential cache refresh by clicking Add -> GitHub Repository -> Refresh in the project canvas. This is a different step from the account-level disconnect you already performed.
19 days ago
This thread has been marked as private. Any further activity in this thread will only be visible to you and Railway employees.
Status changed to Awaiting User Response Railway • 19 days ago
Railway
Your other services in this project (chen_eating_backend, huahan_backend, huahan_frontend) have recent successful deployments, so your GitHub App installation and account-level connection are working. The "Bad credentials" error is isolated to sv-frontend and sv-backend. Try disconnecting the GitHub repo from those specific services in each service's Settings tab, then reconnecting it. You can also force a credential cache refresh by clicking Add -> GitHub Repository -> Refresh in the project canvas. This is a different step from the account-level disconnect you already performed.
19 days ago
Seems it still doesn't work. I've set all repositories access. And SV_2026 can be seen on railway.
Status changed to Awaiting Railway Response Railway • 19 days ago
19 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 19 days ago
19 days ago
If SV_2026 is visible in Railway, repo visibility is probably not the issue anymore.
Since only sv-frontend and sv-backend fail while the other services deploy, I’d treat it as stale source config on those two services. For each failing service: Settings -> Source -> disconnect the repo, save, then connect the repo/branch again from that service. After that, trigger Deploy latest commit, not just retry the old failed deploy.
Also check if those two services still point to an old repo id or old branch name from before the GitHub app reinstall. Seeing the repo in the picker doesnt always mean the old service source token got refreshed.
Status changed to Open chandrika • 18 days ago
Status changed to Solved chandrika • 18 days ago