17 days ago
I run a ticketing software on Railway. This error started to appear out of the box today. This error is thrown during my traffic spikes, so is this somehow related to the latest changes on Railway related to DDOS? If it is, then is there a way to fix it?
It has created a big mess for us.
9 Replies
17 days ago
I disabled the "Railway Domains" feature flag and haven't seen the error for an hour now. I don't know if it really fixed it but you can try disabling that as well.
Attachments
rahul-webd
I disabled the "Railway Domains" feature flag and haven't seen the error for an hour now. I don't know if it really fixed it but you can try disabling that as well.
17 days ago
Railway domains has nothing to do with the varnish page.
17 days ago
Huh, I thought since the DDoS feature was released with Railway Domains, so maybe it was inclusive. Anyway, then this DDoS feature should be an explicit setting that the developer can configure himself.
17 days ago
It was released in the same changelog, but they are mutually exclusive features.
I had this error 30 minutes ago, so I disabled the Cloudflare proxy, and that fixed it for me
And only some locations were affected. SEA had this error, Central Europe was working
17 days ago
Seriously though, these kind of features should be tested a lot more before releasing. I am seeing a phase in Railway's strategy where it's becoming similar to Vercel. It's the second time this month I have faced this kind of issue, where it wasn't our software but Railway. Earlier, it was an Internal Connection related bug.
The issues felt by customers at such peak hours become unacceptable.
It only makes the team think of switching the provider.
