Public updates from vendor feeds, with related items from the same catalog.
Here is the list of fixed issues in this release.
| Issue | Description |
|---|---|
1031565 | After upgrading to appliance version 135.0.0, a timing issue during appliance startup could cause the URL database updater service to fail, resulting in the data plane (DPOP) stopping traffic processing. This occurred when an internal directory was created with incorrect permissions due to the order in which system components started up. This issue is now fixed. The required directories are now created with the correct permissions during initialization, ensuring the URL database updater starts reliably regardless of component startup order. |
1030520 | Fixed an issue where certain sites became unreachable due to an LFS configuration mismatch when LFS was enabled on the global tenant but disabled on the appliance. |
994372 | A high-severity "Diagnostic Agent Health" alarm appeared on the tenant dashboard roughly every 6 hours and cleared on its own after about 5 minutes. The diagnostic agent was healthy throughout — no data was lost and no functionality was affected. The alarm was a false positive. This issue is now fixed and the agent now re-establishes its connection immediately when the gateway closes it, completing recovery in seconds rather than minutes. The agent's health status remains healthy throughout the reconnect, so the spurious alarm no longer fires. |
916659 | Fixed an issue where after an appliance upgrade, the Diagnostic Agent's manually disabled state was not preserved, causing unexpected error logs and alarms. Administrators who had intentionally disabled the service needed to re-disable it after every upgrade. |
848972 | When TSS is enabled and Large File Scanning (LFS) is enabled in the Netskope UI, but LFS is disabled in the DPoP CLI, the proxy still inspected files larger than 16 MB. This issue is now fixed. |
More recent public updates for Netskope.