a year ago
I’m experiencing an issue when attempting to create a new service by deploying from GitHub. Upon initiating the process, the repositories start loading; however, since we have a large number of repositories, the process seems to exceed the 30-second limit and results in a 504 Gateway Timeout error.
Could you please advise on how to resolve this or suggest an alternative approach to load the repositories without hitting the timeout?
13 Replies
a year ago
Hi Jean Michael,
We're investigating and will follow up here soon. Out of curiosity, approximately how many repos does your GitHub organization have?
Regards,
Christian
Status changed to Awaiting User Response Railway • 12 months ago
a year ago
Hey Christian,
Sorry for the delayed response.
As an owner of my organization, I have access to around 1.8k repositories. For other users with access to fewer repositories, the loading works perfectly.
Let me know if there’s any way to work around this!
Status changed to Awaiting Railway Response Railway • 12 months ago
a year ago
Hi Jean Michael, I have created a ticket internally for us to work on this. We are looking at ways to make this experience better.
Status changed to Awaiting User Response Railway • 12 months ago
a year ago
An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!
Status changed to In Progress Railway • 12 months ago
a year ago
Thanks!
Status changed to Awaiting Railway Response Railway • 12 months ago
Status changed to Solved unicodeveloper • 12 months ago
Status changed to Awaiting Railway Response jeanmmayer • 12 months ago
a year ago
not sure why it was marked as solved, but i'm still facing the issue
a year ago
You are right. Looking forward to getting this resolved as soon as possible after the winter break.
Status changed to Awaiting User Response Railway • 12 months ago
a year ago
Update: An internal ticket linked to this thread has been changed to Completed.
Status changed to Awaiting Railway Response Railway • 11 months ago
a year ago
We've fixed this - closing the ticket!
Status changed to Awaiting User Response Railway • 11 months ago
Status changed to Solved parmstar • 11 months ago
Status changed to Awaiting Railway Response jeanmmayer • 11 months ago
a year ago
This is taking longer than I expected from you guys.
Over a month to solve a simple issue that is blocking me.
Railway is useless for me if I, literally, can't deploy stuff.
10 months ago
I'm escalating this now - I thought we had a fix in as the linear ticket was marked as done. Give me a few to find out what's going on.
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
Update: An internal ticket linked to this thread has been changed to Todo.
Status changed to In Progress Railway • 11 months ago
10 months ago
Hi!
So the current solution is to configure the GitHub integration to only select certain repos. That will get you around the timeout issue which we are looking into fixing more broadly now.
https://github.com/apps/railway-app/installations/select_target
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
Update: An internal ticket linked to this thread has been changed to In Progress.
10 months ago
Update: An internal ticket linked to this thread has been changed to Completed.
Status changed to Awaiting Railway Response Railway • 11 months ago
10 months ago
Hi there, sorry for the wait and for closing this prematurely on accident! I misread an issue update.
We've just merged a fix for this. You may now copy/paste any GitHub repo URL you've given Railway access to into the command palette to deploy it.
I've attached an example with one of my personal repos.
Thank you for your patience and let me know if this solution works for you!
Attachments
Status changed to Awaiting User Response Railway • 11 months ago
Status changed to Solved parmstar • 11 months ago