Home / Guides / WebSocket fallback

Network connection

WebSocket timed out, but HTTPS fallback works

The persistent real-time connection failed, so the app switched to ordinary encrypted HTTPS requests. It may be a performance warning or evidence of unstable networking.

Updated July 11, 2026 · 4 min

Does it block work?

If chat, tools, and login all work, it may only affect latency or efficiency.
If messages interrupt, tools fail, or the app spins indefinitely, inspect the network path.

Plain-English versionWebSocket is a continuous call. HTTPS fallback is a series of short request-and-response calls. The app can still work, but behavior may be slower or less stable.

Safe investigation order

Test without a VPN or proxy after recording the original settings.
Check HTTP_PROXY, HTTPS_PROXY, and NO_PROXY for conflicts.
Try another network to separate device settings from router policy.
Check whether a firewall blocks WebSocket upgrade requests.
If HTTPS also fails, inspect DNS and certificates.

Success checks

The warning disappears, or fallback is proven stable for all workflows.
Repeated chats and tool calls complete without interruption.
The result is reproducible and tied to proxy, VPN, firewall, or network.