How do I resolve the error “WebSocket unable to connect”?

Modified on Fri, 2 Feb at 11:34 AM

This error message indicates that you are likely working behind a proxy that doesn’t support the WebSocket protocol. In this case, the device connections will switch to the HTTP protocol. You will notice that although the lab speed is reasonably good and latency moderate, the lab VMs are slow to react to mouse movements or typing.


The switch to HTTP means that instead of having a constantly open connection passing data back and forth, the system sends and receives updates one request at a time.


Possible solutions

  • Do not use a VPN.
  • Connect to a proxy server that supports WebSockets.

If these solutions don’t work, open a support ticket.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article