I got this error! I tried reloading, but it didn’t solve the problem. The page still won’t open.

Here are step-by-step troubleshooting instructions for the "WebSocket close with status code 1006" error in the QuantConnect workbench:

1. Confirm Internet Stability
   • Power-cycle your router/modem and reconnect your computer to the network.
   • If possible, switch to a wired Ethernet connection or a different Wi-Fi network to rule out local interference.
   • Test another real-time WebSocket site (e.g., a public echo server) to verify the connection can stay open for several minutes.

2. Rule Out Temporary QuantConnect Maintenance
   • Check the QuantConnect status page (status.quantconnect.com) for any incidents.
   • If an outage is reported, wait until it is resolved before further troubleshooting.

3. Refresh Browser Session Data
   • Fully close every browser tab connected to QuantConnect.
   • Clear the browser’s cache, cookies, and site storage for *.quantconnect.com.
   • Reopen the browser in an incognito/private window and log in again.
   • If the issue disappears in private mode, disable or remove conflicting extensions (ad-blockers, privacy filters, script blockers, etc.) in normal mode.

4. Update or Change Browsers
   • Verify you are running the latest stable version of Chrome, Edge, Firefox, or Safari.
   • Disable experimental browser flags that affect networking (e.g., QUIC) and retest.
   • If the error persists, try a different supported browser to isolate a browser-specific problem.

5. Check Corporate VPN, Proxy, and Firewall Rules
   • Temporarily disconnect from VPN or corporate proxy and retry the workbench.
   • Ensure outbound TCP ports 80 and 443 are open and not subjected to deep-packet inspection or idle-connection timeouts.
   • Whitelist the following QuantConnect domains in the firewall/proxy:

   • www.quantconnect.com
   • api.quantconnect.com
   • cloud.quantconnect.com
     • If you administer the firewall, raise the idle timeout for WebSocket connections to at least 300 seconds.

6. Verify Local Security Software
   • Pause or create exceptions in antivirus, endpoint protection, or internet-security suites that can terminate long-lived TCP connections.
   • After confirming the platform works, re-enable protection one component at a time to identify the culprit.

7. Reduce Browser Tab and IDE Activity
   • Close other cloud IDEs, streaming sites, or heavy WebSocket apps that may exhaust the browser’s WebSocket limit (typically 255 connections per origin).

8. Retest in a Clean Environment
   • Create a fresh user profile in your browser or use a different operating-system account to confirm the issue is not linked to user-profile corruption.

9. Gather Diagnostic Information if the Problem Continues
   • Open your browser’s DevTools → Network → WS (WebSocket) tab and reproduce the error; capture a HAR file.
   • Note the exact UTC timestamp, any console errors, and the version/OS details of your browser and operating system.

10. Contact QuantConnect Support
    • Provide the HAR file, timestamps, screenshots, and a description of every step already taken.
    • Mention whether the error occurs only in the workbench or also in backtest/live result streams.
    • Include your workspace URL or project ID so the support team can inspect server-side logs.

Following these steps systematically resolves the vast majority of WebSocket 1006 errors; contacting support with the requested diagnostics should expedite any remaining investigation.