4 months ago
I’m seeing recurring WebSocket disconnections (code 1006 ) in my service.
There’s an odd pattern: disconnections spike daily around 5pm eastern, and rarely occur before or after that window. There’s no cause (that I can see) for this in my application, and it doesn't appear to be correlated with resource usage either.
Is there some regular job being run on Railway’s side that may explain this strange pattern or generally cause WebSocket disconnections?
8 Replies
4 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
4 months ago
Hello,
That would be around the time we cycle the proxies. We are aware of this issue and will be looking into mitigations.
Best,
Brody
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
Appreciate the quick response - anything we can do in the short term? This is impacting our ability to serve customers.
Even just shifting the proxy cycling outside of core business hours, while maybe not a perfect solution, would really help reduce business disruption.
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Shifting the cycle time of the proxies wouldn't be a solution, unfortunately. It may mitigate the issue for you, but it would just move it to someone else's business hours, so we will opt to keep the time it has always been set to.
A solution could be to deploy the Cloudflare tunnel, thus bypassing our proxy.
https://railway.com/deploy/cf-tunnel
Again, I want to acknowledge that this situation in general is not ideal, and I apologize for that.
Status changed to Awaiting User Response Railway • 4 months ago
4 months 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 • 4 months ago
3 months ago
Hey, small update here. As mentioned, we would restart the proxy every day. We have changed that to be a little more intelligent with those restarts. Now, restarts are performed only when needed. In practice, that means fewer restarts.
Status changed to Awaiting User Response Railway • 4 months ago
3 months 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 • 3 months ago
3 months ago
🛠️ The ticket Websocket traffic disruptions has been marked as triage.
2 months ago
🛠️ The ticket Websocket traffic disruptions has been marked as backlog.
a month ago
❌ The ticket Websocket traffic disruptions has been marked as canceled.