a month ago
Today my new commits stopped deploying and when selecting a repo I see "Bad credentials"
In Deployments tab, I can see that Railway picked a new commit, but failing to pull the code somehow.
I have tried
- Deleting Railway app and installing from scratch
- Removing access to repo, granting access to repo
- Pushing new commits
- Creating a new service/project
- Deploying a different repo from the same org works
- Renaming the repo. Railway immediately picks up a new name, but gives same error
I am running out of options, this is incredibly frustrating, it used to work fine until an hour ago. Example service https://railway.com/project/3de2c12c-c91f-4076-84e4-c9c42cba168b/service/3f9f1cbd-9142-4017-90d0-1e407a812545?environmentId=e2465b45-4e4e-4e2c-b6b8-1bbf37a0933b
Attachments
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
After reconnecting multiple times, I no longer see the same error, but deployments are stuck and failed after 5 minutes. Build log says "Railway can't access {org}/{repo}. Reconnect the GitHub repository under Service Settings → Source, or reinstall the Railway GitHub App and grant it access to this repo."
But I have done it many times! Please help
Attachments
a month ago
same problem
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
25 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 • 25 days ago