Krev
Don't auto-enable the new proxy. It's bad for my app and I purposefully leave it off!
@blank (revived) and I get this TIMEOUT error too, we reported it in another thread a long time ago and our fix was to stick to Legacy network, though that option seems to be removed now. Since that option is removed, our semi working solution is to use http proxies when making requests from another hosting platform to Railway.
This happens when sending a lot of requests from a single IP to Railway. It was never a problem in Legacy, not sure why it is now.
Note: even with 5k proxies rotating, we still get timeout errors. Not often but it’ll come here and there
86 replies