Troubleshooting

WebSocket upgrade requests fail or hang

Confirm both startHttpServer and startWebSocketServer bootstrap flags are true, and that @quik/http-express is loaded and boots before @quik/websocket-express.

send()/broadcast() silently do nothing

Verify at least one client has completed the WebSocket upgrade to websocket.path — send() targets a specific connectionId and broadcast() only reaches currently open connections.

Clients disconnect after the heartbeat timeout

Same heartbeat behavior as @quik/websocket applies here — see @quik/websocket Troubleshooting.

Adapter not found / getWebSocketEngine() returns nothing

@quik/websocket-express must be included in the bootstrap modules list — including @quik/websocket alone does not register a server adapter.