Feature Description
WebSocket Debug Client
Connect to ws/wss endpoints, send messages, and inspect realtime responses.
Debug ws/wss connections, send messages, and inspect realtime server responses.
When ws/wss Is Blocked
- If the page is HTTPS, browsers block ws:// mixed content. Use wss:// instead.
- Untrusted TLS certificates break wss handshakes. Use a valid cert and correct server time.
- If your server validates Origin, add the current site domain to the allowlist.
- Browser WebSocket cannot set custom handshake headers. Use query params, cookies, or Sec-WebSocket-Protocol for auth.
- If proxies/CDN block upgrade, enable WebSocket pass-through (Upgrade/Connection) on Nginx/gateway.
Common use cases
- Use this page when you need to test whether a WebSocket endpoint connects, accepts messages, and returns data correctly.
- It is useful for ws/wss troubleshooting when a browser-based test is faster than writing temporary client code.
- During backend collaboration, seeing sent and received messages in one place makes realtime issues easier to narrow down.