> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/single-server-deployment/post-installation-checklist/troubleshoot-websockets.md).

# Troubleshoot WebSockets

Troubleshoot Cortex XSOAR 6.15 WebSocket disconnects, slow responses, and missing real-time browser updates.

A WebSocket communications protocol is used in Cortex XSOAR for bi-directional data transfer between the client browser and the server. WebSocket communication enables data to auto update without refreshing the browser.

If a user experiences a slow response from the Cortex XSOAR server and does not receive data updates on certain pages and actions, the WebSocket may be disconnecting. The causes of WebSocket disconnects are:

* The network proxy killing the WebSocket connection.
* Slow connection between server and client.

Solutions:

* If the network proxy is the cause, adjust network proxy settings to allow WebSocket connections.
* Check the throughput between server and client.
* Verify the **System Diagnostics** page does not show alerts for large incidents, context, tasks, etc.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/single-server-deployment/post-installation-checklist/troubleshoot-websockets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.