> 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.14/onboard-cortex-xsoar/single-server-deployment/post-installation-checklist/troubleshoot-websockets.md).

# Troubleshoot WebSockets

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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.