> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/library-packs/network-and-connectivity/zscaler-troubleshooting.md).

# Zscaler troubleshooting

## Problem <a href="#zscalertroubleshooting-problem" id="zscalertroubleshooting-problem"></a>

Zscaler is one of the most recognized cloud security providers, securing millions of employees’ access to their applications from their devices. However, Zscaler sometimes silently disconnects and de-authenticates without the user’s knowledge. This results in the user losing access to internal applications.

It is now common for employees to suddenly lose access to their critical business applications without them understanding why. Support teams incessantly face urgent L1 tickets that waste IT and employees’ time.

## Solution <a href="#zscalertroubleshooting-solution" id="zscalertroubleshooting-solution"></a>

Ensure Zscaler is running and connected on all devices in the landscape by monitoring your employees’ Zscaler client connectivity, performance, and ability to authenticate.

With real-time visibility into their current status, you can proactively repair, restart, or re-authenticate Zscaler clients and drastically reduce incoming Zscaler-related tickets.

## Key benefits <a href="#zscalertroubleshooting-keyfeatures" id="zscalertroubleshooting-keyfeatures"></a>

* Real-time visibility into Zscaler installations, performance, connectivity, and errors.
* Dedicated dashboard to monitor connection failures and network traffic.
* A detailed breakdown of ZIA and ZPA service errors preventing successful authentication.
* Remote Actions to remotely start Zscaler clients and prompt users to re-authenticate.
* Network and desktop applications for in-depth adoption stability and connectivity monitoring.

## Get started <a href="#zscalertroubleshooting-changelog" id="zscalertroubleshooting-changelog"></a>

Configure and start using your packs by following these links:

{% content-ref url="/pages/9X8cMQRyITvWFsXVfb8G" %}
[Configuration guide: Zscaler troubleshooting](/library-packs/network-and-connectivity/zscaler-troubleshooting/configuration-guide-zscaler-troubleshooting.md)
{% endcontent-ref %}

{% content-ref url="/pages/rUYTHJ5JkNY2zL9LUWuo" %}
[Usage guide: Zscaler troubleshooting](/library-packs/network-and-connectivity/zscaler-troubleshooting/usage-guide-zscaler-troubleshooting.md)
{% endcontent-ref %}


---

# 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 by asking a question.

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

```
GET https://docs.nexthink.com/library-packs/network-and-connectivity/zscaler-troubleshooting.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 `automate deployments from our CI pipeline` 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.