Loading...

tools / websocket-debug

WebSocket Debugger

Analyze WebSocket handshakes, close codes, auth headers, reconnect loops, ping/pong timing, and message samples.

P1API / NetworkHigh severity
85
debug signal score
3 signals

3 signals detected. Start with handshake failure.

Detected signals

Handshake failure

The HTTP upgrade request is failing before the socket opens.

Inspect upgrade headers, auth, origin, proxy/load balancer support, and selected subprotocol.

Close code detected

The socket closes with a meaningful code or abnormal closure.

Map the close code to server logs and confirm whether the close was server, client, or proxy initiated.

Reconnect loop

The client is repeatedly reconnecting.

Add jitter, cap retries, and inspect why the first stable connection is lost.

Highlighted lines
line 1
WebSocket connection failed: 403
Handshake failure
line 2
Sec-WebSocket-Protocol: bearer
Handshake failure
line 3
close code 1006 abnormal closure
Close code detected
line 4
reconnect attempt 12
Reconnect loop
Fix checklist
Inspect upgrade headers, auth, origin, proxy/load balancer support, and selected subprotocol.
Map the close code to server logs and confirm whether the close was server, client, or proxy initiated.
Add jitter, cap retries, and inspect why the first stable connection is lost.
Capture the initial HTTP upgrade response.
Record close code, reason, and exact timing.
Check proxy and load balancer WebSocket support.

DebugTools product

WebSocket Debugger

WebSocket Debugger is a focused DebugTools mini-product for developers. Analyze WebSocket handshakes, close codes, auth headers, reconnect loops, ping/pong timing, and message samples.

Use cases

  • Debug request, response, header, status, redirect, and payload problems.
  • Create a small reproduction before changing client or backend code.
  • Compare working and failing network evidence without leaving the browser.

How it works

  • Paste or load the snippet you want to inspect in WebSocket Debugger.
  • Run the tool in the browser and review the highlighted output.
  • Copy, export, or turn the result into the next debugging step.

Privacy

  • WebSocket Debugger is local-first. The core workflow runs in your browser and does not require sending pasted content to DebugTools servers.

This tool history

Recent Websocket Debug sessions

Only visits for this tool are shown. Pasted content, tokens, request bodies, and logs are not stored here.

Loading this tool history...