websocket problem 1006

Question

Project: 4b640aaa-c1cf-41f3-8d70-c353abfa1bc2

Building a collaborative editor (NextJS + Lexical + y-redis) on Railway. WebSocket connections fail with **code 1006** in production but work perfectly locally.

## **The Problem**
1. ✅ Auth works - HTTP 200
2. ✅ WebSocket upgrade completes 
3. ✅ Connection opens
4. ❌ **Immediately closes with 1006** when server sends initial Yjs sync messages

## **Error Details**
```
🔗 WebSocket connection opened for user: {...}
📤 Sending SyncStep1...
❌ WebSocket connection closed: { code: 1006, reason: 'abnormal closure' }
HTTP: 499 "client closed request before server response"
```

## **Railway Context**
**Confirmed Railway WebSocket bug** reported June 20th with identical symptoms. Railway claimed it was fixed, but still experiencing it.

## **What I've Tried**
- ✅ Disabled compression (`uws.DISABLED`)
- ✅ Reduced timeout to 30s  
- ✅ Added delays before sync messages
- ❌ **Still fails when sending binary Yjs data**

## **My Theory**
Railway's proxy has issues with **binary Yjs protocol messages**. Connection opens fine, but terminates when sending sync data.

## **Questions**
1. Anyone else having Railway WebSocket issues?
2. Alternative hosting for WebSocket-heavy apps?
3. Tried both US West/East region, region issue?
4. Disabled RailwayMetal Edge, maybe thats the problem?

```javascript
// Works locally, fails on Railway
app.ws('/:room', {
  compression: uws.DISABLED,
  idleTimeout: 30,
  // ...sends binary Yjs sync messages
})
```

Blocked for 3+ days on this! Any help appreciated 🙏

#websockets #yjs #lexical