websocket-debugger

Debug WebSocket connection failures by verifying the handshake completes, checking ASGI/Daphne configuration, validating JWT authentication headers through TokenAuthMiddleware, and inspecting Django Channels consumer logs for routing or connection errors.

Missing messages typically indicate Redis channel layer misconfiguration, channel group subscription issues, or pub/sub delivery problems. Trace message flow end-to-end, inspect Redis pub/sub logs, verify channel groups are receiving broadcasts, and check for dropped WebSocket frames.

Validate JWT tokens by inspecting auth headers at the WebSocket handshake, confirming TokenAuthMiddleware processes credentials correctly, testing token validity before connection, and monitoring middleware logs to catch authentication errors before the consumer receives frames.

Diagnose delays by monitoring Redis pub/sub delivery latency, tracing message routing through channel groups, checking for backpressure in consumers, and reviewing Daphne logs for frame buffering or connection state issues causing stream interruption.

Identify routing issues by validating consumer routing configuration, inspecting channel layer message delivery logs, verifying channel group memberships, and testing frame transmission end-to-end with Redis pub/sub monitoring to catch dropped or misdirected messages.

Yes. Effective debugging requires Django Channels with ASGI, Daphne server, Redis channel layer for pub/sub, JWT-based TokenAuthMiddleware for authentication, and access to core project modules including consumers, routing configuration, middleware, and background tasks.