ZScaler Compatibility

Overview

Nectar's Endpoint Client is currently not compatible with Zscaler Internet Access (ZIA) or Zscaler Private Access (ZPA). Customers using Zscaler may experience unexpected behavior, failed connections, or blocked traffic when attempting to run the Nectar Endpoint Client.

Root Cause

Zscaler's security stack includes traffic inspection, SSL/TLS interception, and strict access policies. These interfere with how the Nectar Endpoint Client communicates with its servers, particularly when:

• Establishing secure WebSocket or HTTPS sessions

• Transmitting telemetry or media quality data

• Attempting to auto-discover or register with the Nectar platform

Zscaler may inspect or block this traffic, causing the Endpoint Client to fail or hang.

Recommended Actions

If your organization uses Zscaler and requires the use of Nectar’s Endpoint Client, consider the following options:

1. Bypass Configuration

   Work with your Zscaler administrator to whitelist or bypass the following for Nectar traffic:

   • All traffic to *.nectar.services

   • Specific IP addresses or domains used by your instance of the Nectar platform

   • Any relevant ports (typically 443 and 40006 ports)

2. Split Tunneling

   If you are using Zscaler in conjunction with a VPN, split tunneling may be used to exclude Nectar Endpoint Client traffic from Zscaler inspection.

3. Run Outside Zscaler Control

   As a last resort, install and run the Nectar Endpoint Client on a device not subject to Zscaler filtering, such as a test machine on a guest Wi-Fi network or on a direct internet connection.

Status

This is a known limitation.  Nectar Engineering is investigating potential solutions or workarounds, but at this time there is no ETA for a native fix.

Need Help?

If you are unsure how to configure Zscaler to allow Nectar traffic or need assistance identifying what traffic should be bypassed, please contact Nectar Support with the following information:

• A description of your Zscaler setup

• Endpoint Client version

• Logs from the affected system

• Network trace, if available

We are actively monitoring this issue and will update this page if a compatibility update becomes available.