Drag in the log bundle exported by the Zscaler Client Connector (or pick it manually). You'll get an instant, severity-sorted list of detected failures - tunnel, DNS, PAC file, authentication, posture, SSL, AV/firewall interference - each with a recommendation.
Your logs never leave your machine: unpacking and analysis run entirely in the browser, no data is transferred.Easiest: drag in the ZIP file exported by ZCC directly. Individual .log/.txt files also work.
Need versioning, four-eyes approval and rollback? CentaurNexus is the sovereign cockpit for your Zscaler world. EU hosting, GDPR-compliant.
View live demoIt unpacks the log bundle exported by the Zscaler Client Connector directly in your browser, parses the contained log files (e.g. ZSATunnel, ZSAService, ZSAUpm) and lists detected failure patterns by severity: tunnel connection failures, DNS failures, PAC file errors, authentication loops, posture failures, SSL certificate errors, AV/firewall interference, captive portal detection, and ZCC upgrade problems.
No. Unpacking and analysis run entirely in the browser (JavaScript); there is no server round trip. ZCC logs contain device names, user identifiers and internal hostnames - which is exactly why client-side processing here isn't an option, it's the requirement.
In the ZCC tray icon, use the gear menu "About" or "Advanced" and choose "Export Logs" or "Collect Logs". The Client Connector produces a ZIP archive with all relevant log files, which you drag and drop here.
No. The tool only analyzes the ZCC log files that live locally on the endpoint, which any user can export themselves. No access to the Zscaler admin console or OneAPI is required.
