Netsweeper is pleased to announce the Netsweeper 8.2.12 GA Release. This release focuses on further stability improvements in order to refine the Netsweeper 8.2 GA product. All customers are strongly encouraged to upgrade to the 8.2.12 GA release in their test environments and proceed to upgrading their production deployments. The 8.2.12 GA release only fixes critical variances found that impact customer production environments and only introduces new features or functionality if they are needed for stability..
Netsweeper will be continuing to focus on the 9.1 release cycle throughout 2025. The initial version Netsweeper 9.1.1 was released in February 2025 and our goal is to have the first 9.1 GA release happening early in the 2026 calendar year. For an ongoing list of the new features and improvements in the 9.1 release, please refer to our 9.1 New Features documentation.
If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (support@netsweeper.com).
See Also
8.2 New Features Combined and Summary of 8.2 New Features
Downloads
https://repo.netsweeper.com/releases/centos/iso/netsweeper-el8-x86_64-8.2.12-1.iso (8.2.12 md5 checksum) (8.2.12 sha256 signature)
Changelog 8.2.12
| Issue Type | Ticket | Summary |
|---|---|---|
| Bug | NS-824 | Creating numerous custom Deny Pages that each contain a large amount of data could cause the Deny Page framework to run out of memory. |
| Improvement | NS-1344 | Improved 'progress_data' processing as well as prioritizing of Report processing 'wait times' in order to facilitate large numbers of Reports per page. This affects all Report types. |
| Bug | NS-1575 | Saving a List Entry could fail due to applying an incorrect 'Entry Type' Restriction for specific Request Parts. |
| Bug | NS-1576 | The 'Default Action' List Entry Type could not be selected due to an incorrect restriction. |
| Task | NS-1976 | The 8.2.12 release ticket |
| Improvement | NS-1978 | Renamed Accounts > Account Tokens to Access Tokens to ensure they are referred to as 'Access Tokens' everywhere in the product. |
| Bug | NS-2049 | WebAdmin API versions 4-8 did not have the needed format parameters for: agent_config_delete, agent_config_query, policy_sharedlist_add, policy_sharedlist_delete, policy_sharedlist_delete_all, account_template_group_query, account_template_ip_query APIs. |
| Bug | NS-2071 | SysOp Account IP Range restrictions were not being properly enforced when created by SysOps. |
| Bug | NS-2094 | Sysops without 'Client Type' permission(s) would see the '+' (Create) button when viewing Clients in a Group. Selecting it would result in an Error page being served. |
| Bug | NS-2095 | On the scheduled, demand, continuous reports pages we can queue up many Progress Data calls and do not cancel prior calls when advanced search is used. |
| Bug | NS-2105 | When adding a new Reporter server with the same ID as a disabled Reporter server, we would delete existing instance data. |
| Bug | NS-2110 | The nsroutes service would load expired entries when loading data from the WebAdmin via WebDB API calls. |
| Bug | NS-2111 | The nsroutesctl service was failing to set the hostname when run via the 'systemctl start nsroutesctl' command. |
| Bug | NS-2128 | The Policy Service Partial ICAP request processing was causing requests to fail, and needing to be retried. |
| Bug | NS-2134 | A Policy Server connection failure could occur when a HTTP request exceeds the nsproxy.conf policy_max_request_length setting. |
| Bug | NS-2135 | The 'Enabled Client Types', 'Allow Report Email Data', and 'Report Authorization' Settings did not have any default values when upgrading from 7.2. Default values have now been properly assigned. |
| Improvement | NS-2154 | The reporter could segfault when stopped while actively generating Reports, due to the shutdown process calling functions as a single handler. |
| Improvement | NS-2171 | Disabled some redundant error checking regarding the Workstation Agent, WebDB, and the dynamicdns.php entry points. |
| Bug | NS-2179 | The systemstatus table on an active WebAdmin with many users using the Status and Services windows could cause the Status to fail due to database 'auto_increment' exhaustion. |
| Bug | NS-2182 | If the WebAdmin language was set to an invalid lanauge and there was no HTTP header for HTTP_ACCEPT_LANGUAGE, the user would get a translation error. We now set the language to the default en_US in this case. |
| Improvement | NS-2200 | Disabled some redundant error checking regarding the WebDB and the dynamicdns.php entry points. |
Copyright © 2026 Netsweeper Inc. All rights reserved.
Confidential and Private information. Distribution of the information contained herein is strictly prohibited.