8 months ago
Hello.
I've started getting Abnormal closure of my websocket connections. The closure code is 1006.
What could be the reason.
No changes on app side. I've rolled back the version to check if it is app side issue. But it is reproduced with older version as well which was working earlier.
7 Replies
8 months ago
I guess this wasn't fully fixed: https://status.railway.com/cmc4jjd1d000pk5gq7kigdz1s which causes instability with web socket connections.
8 months ago
Yes, getting same issue!
8 months ago
Hello,
That incident is unrelated.
Can you try disabling the Metal Edge? This can be done from within the Public Networking section in your service setting by clicking the undo button besides the Metal Edge text.
Status changed to Awaiting User Response Railway • 8 months ago
brody
Hello,That incident is unrelated.Can you try disabling the Metal Edge? This can be done from within the Public Networking section in your service setting by clicking the undo button besides the Metal Edge text.
8 months ago
Downgraded to Google Cloud edge - now web socket works more stable. It was working with Metal Edge earlier
Status changed to Awaiting Railway Response Railway • 8 months ago
Status changed to Awaiting User Response Railway • 8 months ago
8 months ago
Hello all,
We have fixed the regression on the Metal proxy and confirmed that WebSockets and SSEs do not drop anymore.
Please re-enable the Metal Edge if you had disabled it.
brody
Hello all,We have fixed the regression on the Metal proxy and confirmed that WebSockets and SSEs do not drop anymore.Please re-enable the Metal Edge if you had disabled it.
8 months ago
Thank you. Confirming that the issue is not appeared anymore for Metal edge.
Status changed to Awaiting Railway Response Railway • 8 months ago
Status changed to Solved brody • 8 months ago