a month ago
Hi Railway support,
Service connection to louisvandeputte-sketch/everyjobapp shows "Bad credentials" in Settings → Source. Fresh deployments fail immediately at the snapshot stage with "repository not authorized."
Failed deployment ID: 51d145e0-2e43-4d78-9973-e51074a25c0a
The confusing part:
Railway GitHub App is installed with "All repositories" access and full read/write permissions.
Account → Integrations shows GitHub as connected.
Redeploys of cached snapshots still work — only fresh clones fail, so the stored token for this service appears invalid.
A successful deploy ran ~3 minutes before the token broke, without any change on my GitHub side.
Already tried: verified App permissions, suspended/unsuspended the App installation — no effect.
Can you check why the stored token became invalid, and force-refresh it on your side without me having to fully disconnect + reconnect the source?
Thanks!
5 Replies
a month ago
I meet the same problem
a month ago
Your "everyjob-website" service in a separate project also failed at the same time, which confirms the token invalidation is at the workspace-level GitHub App installation, not specific to one repo. We do not have the ability to force-refresh GitHub App tokens on our side. To resolve this, disconnect and reconnect the repo in your service's Settings, or if that doesn't work, uninstall and reinstall the Railway GitHub App as described in our troubleshooting docs.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I disconnected Github, and after succesful reconnect I keep seeing 'bad credentials'. Can you please investigate this asap. Thanks!
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
we’re having same issue with GitHub deployments across multiple Railway services in the same project/workspace.
All services connected to the GitHub repository are failing during the “Initialization > Snapshot code” step with:
[ERROR] ##NOT-AUTHORIZED## repository not authorized
In each service settings, under Source, the repo is shown as connected, but the production branch section shows:
Bad credentials
Repository:
What we already tried:
- disconnected and reconnected the repository from the Railway service settings
- uninstalled the Railway GitHub App from GitHub
- reinstalled the Railway GitHub App
- granted Railway access to all repositories
- confirmed the repository is included in the Railway GitHub App installation
- logged out and back into Railway
- retried deployments after reconnecting the repo
The issue still persists across all GitHub-connected services, not just one service.
Could you please check if there is a stale or broken GitHub installation/token mapping on Railway’s side for this workspace/project/repository? It looks like Railway can still display the repository as connected, but cannot authorize the snapshot/clone step.
Affected:
- Repository: delavegaOpengl/betting
- Services affected: all services connected to this GitHub repo
- Error: ##NOT-AUTHORIZED## repository not authorized
- Deployment stage: Initialization > Snapshot code
- Source settings status: Bad credentials
Thanks.
a month ago
Hi there! GitHub is currently experiencing an issue with app installation token authentication which is causing these errors. You can track it here: https://www.githubstatus.com/incidents/k5z4d1v1tqmt. No action needed on your end, deploys should recover once GitHub resolves this. Apologies for the trouble!
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago