...
What is WebSocket?
WebSocket allows you to send and receive messages is a computer communications protocol that enables messages to be sent to and from the server. Basically, it is a way means of communication between you and the server. The WebSocket specification defines an API for establishing "socket" connections between a web browser and the machine. In other words, there is a persistent connection between you and the server, and both parties sides of the connection can start sending data at any time. The XTM Workbench application uses WebSockets to establish the connection.
The WebSockets are quite sensitive for to some online software that may impact has the potential to affect the connection. Sometimes, the direct cause of the WebSockets disconnections is the software installed on the user - end, such as:
browser plugins/extensions;,
firewalls;,
VPNs (Virtual Private Network);,
CDNs (Content Delivery Network).
When If the disconnects are happeningoccur, it is always a good idea to temporarily disable the software and see if it helpedthat helps. If that does not yield desirable the required results, please, click here follow the basic steps from described in the article.
...
Specifics
Generally, there are a few issues with WebSockets involved, below involving WebSockets. Below are the most common cases:
...
The JSERROR (or JavaScript Error) is usually an issue with a user’s user'’s browser , but it might sometimes it may also be caused by an XTM Cloud front-end bug. In order to To be surecertain, though, the proper investigation is required. As a user, you can help out the XTM support International Support team by providing the relevant information from your side to facilitate the , to speed up issue resolution,.
The error in the browser developer tools usually points to some JavaScript files, indicating that required properties cannot be read. The A blank screen might then be displayed instead of the Workbench application may then give a blank screen, as on in the example below:
...
Browser developer tools - the Console section:
...
Please, click Click here for help.
NO_BROWSER_PING
The NO_BROWSER_PING issue occurs when the XTM Cloud application cannot ping the browser anymore, which leads to the WebSockets disconnection. This is rather usually a user-end issue, and the connection between the browser and XTM Workbench can be blocked by, for example, some software.
Below is the XTM Workbench window with the browser developer tools errors - : the Console section:
...
WebSockets can be tested with online tests: WebSocket tester.
...
In most cases, WebSockets issues occurring on the user-end and the XTM support International Support team is often unable to directly solve such issues. However, sometimes the problems sometimes only seem to lie on at the users ' end, but it eventually turns out that this is an XTM Cloud issue is involved and we need to make some changes. Irrespective of No matter what the root cause is, please, do not hesitate to reach out to contact the XTM support International Support team with all the above-mentioned information gathered up.