5 days ago
Our FastAPI-based WebSocket service, hosted on Railway, has recently started experiencing connection issues. Connections are being closed with error code 1006 (Abnormal Closure) after approximately 20-30 seconds.
The same code was previously running without any issues, but it now consistently experiences disconnections.
We are using the Railway Edge Proxy (Server:
railway-edge).I’ve tested both protocol-level ping-pong and application-level ping-pong mechanisms.
The connection is successfully established but closes shortly after.
1006 Abnormal Closure:
No close frame was received.
This issue started recently.
What is the recommended best practice to prevent abnormal WebSocket closures on the Railway platform?
Has there been any recent change on the platform that could affect WebSocket behavior?
1 Replies
4 days ago
Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.
I've made this thread public so that the community might be able to help with you query.
Status changed to Awaiting User Response railway[bot] • 4 days ago
4 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open jake • 4 days ago
Status changed to Solved muhammetakkurtt • 4 days ago