a month ago
I'm experiencing deployment issues that seem related to the GitHub problems from last week. A backend dev helped reset some bad state then, but now I'm hitting new issues.
Previously, Railway couldn't recognize my repository or read branches. I've tried pushing new commits to trigger updates, but nothing happens. Disconnecting and reconnecting the service didn't help either.
I even deployed a fresh service to test, but the GitHub trigger isn't working ... it won't start builds or pull the repo. When I manually tried to toggle it, I got this error. The old service has the same problem: no builds trigger when PRs merge, new commits are pushed to the branch, or when I switch to a different branch.
5 Replies
a month ago
Hmm I wonder if this is related to caching. We recently had an issue where GitHub was heavily rate limiting us and we implemented longer cache. Could you try removing/readding GitHub from your Railway account at https://railway.com/accounts? Would trigger a force refresh and should be good!
Let me know how that goes!
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Just did and then I got this from github when I tried to sign back in: No server is currently available to service your request.
Sorry about that. Please try refreshing and contact us if the problem persists.
Then when I got routed back to railway this showed up: "Error authenticating with GitHub
Problem completing OAuth login"
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Same issue here
jkulick
Just did and then I got this from github when I tried to sign back in: No server is currently available to service your request.Sorry about that. Please try refreshing and contact us if the problem persists.Then when I got routed back to railway this showed up: "Error authenticating with GitHubProblem completing OAuth login"
a month ago
just tried again and now its fixed
Status changed to Awaiting User Response Railway • about 1 month 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 • 26 days ago