a year ago
Had to switch back our main service back off of metal, not sure why but it seems that it somehow got congested? Not sure how else to describe it, but moving back to non-metal solved the issue. 
3 Replies
a year ago
Hello,
Can you share how you came to that conclusion? what errors where you seeing? did you have static IPs enabled?
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
App wasn't loading, http logs we're showing lots of 499s. I tried redeploying (same amount of errors), and adding a new instance (that made it worse). Then once I switched back to non-metal it all seemed fine. No static IPs
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hey Brandon (long time no see)
It's going to be hard to re-pro this issue without any logs or request-ids, as soon as you see this, you have my permission to tag me directly on Discord. We are going to be migrating everyone over to Metal in the coming months and would love to get to the bottom of this issue before we do the whole migration.
I am going to mark this as solved but please quickly raise.
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved angelo-railway • about 1 year ago