May 6th 2025 - Version 25.2.106.1114$$$$$$Improved$$$Security$$$$$$Webserver$$$We hardened PRTG against open redirect vulnerabilities where URL forwarding to external sites was possible.$$$$$$Improved$$$Sensors$$$$$$Device templates$$$We adapted our device templates so that they also contain the new v2 sensor types. Former deprecated sensors that have an according v2 sensor type as successor were removed from the device templates. For example; when you execute an auto-discovery with device template for Server DNS; the DNS v2 sensor will be added afterwards.$$$VMware Datastore (SOAP) sensor$$$The VMware Datastore (SOAP) sensor now includes limits for the channel Free Space by default. The Lower Warning Limit (%) is set to 10 and Lower Error Limit (%) is set to 5. These thresholds are set by default when you create this sensor type new or when you did not have set custom limits before in a previous PRTG version for this sensor. When you have set custom limits before; those settings will be kept when you update to this PRTG version.$$$Script v2 sensor$$$The Script v2 sensor now supports native executables. This means that the sensor can now run arbitrary executable files (Linux) or * (Windows). The native executable file should be stored on the probe system. On Linux systems; executables require execute permissions to run. To run Python scripts; this sensor requires that Python 3 is within PATH.$$$Sensor status$$$We improved the error message text in the sensor status so you will receive a proper error message instead of a generic one when certain exceptions occur.$$$$$$Improved$$$Server$$$$$$License$$$We improved our license handling and error messages on the License Information page in PRTG. For example; when you want to change your license and the key is not valid or wrong; you will receive an according error message Activation successful - using previous license key. PRTG will then use the previous key as stated in the message instead.$$$$$$Important$$$Sensors$$$$$$SSH INodes Free sensor migration$$$Your SSH INodes Free sensors will be migrated to the successor SSH INodes Free v2 sensors when you update to this PRTG version and higher. We already announced the upcoming sensor migration with PRTG version 25.1.104.1946. After successful sensor migration; your SSH INodes Free v2 sensors will keep the ID; settings and historic data of the former SSH INodes Free sensors. You will receive an according TO DO ticket in PRTG about relevant device template migration and under which path you can find a backup of the original files. For more information about sensor migration; please see the Knowledge Base article: What is a sensor migration?$$$$$$Fixed$$$Server$$$$$$Geo location$$$We fixed an issue for geo location information that was displayed in native language for the according country; region or city. The issue occurred because our location service provider updated their API which had impact on the location language. The locations in the Geo Map will be displayed in English again when you update to this PRTG version.$$$PRTG application server$$$We fixed an issue that occurred with PRTG version 25.1.104.1946 where the application server service stopped running or did not run at all in rare cases; depending on the number of sensors and system resources; for example. As a result; you could not use the new PRTG user interface. You could also observe that the application server was consuming much more memory in these cases.$$$SMTP settings$$$We fixed an issue that occurred when you have set your SMTP server settings to Continue delivery if session is disconnected by client in order to receive email notifications in certain cases. PRTG would cut the connection to the SMTP server before getting any confirmation in those cases. PRTG will now send a QUIT verb to the SMTP server before cutting the connection.$$$$$$Fixed$$$Sensors$$$$$$HTTP Transaction sensor$$$We fixed an issue for the HTTP Transaction sensor that occurred in previous PRTG versions where the sensors went into Down

April 7th 2025 - Version 25.1.104.1961$$$$$$Fixed$$$Sensors$$$$$$SNMP v3$$$We fixed an issue for SNMP sensors that ran into error state in certain cases when you used the SNMP v3 setting for SNMP Version and when you updated to PRTG version 25.1.104.1946. The issue occurred when your devices had the same SNMP engine ID; which could happen after cloning virtual machines with preconfigured SNMP settings for SNMP v3. A possible workaround was to use different user names per switch.$$$$$$Please note that this issue persists in the intermediate PRTG version 25.1.104.1906 that is needed for further PRTG updates. We recommend that you update to this version 25.1.104.1961 soon.$$$$$$Note$$$Installer$$$$$$Security$$$You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:$$$$$$Stable 25.1.104.1961$$$sha256_exe 480637BD026D608FF987BAF3273921C7995934653913EBF42DDD0DA939EFE47A$$$ $$$sha256_zip 6B2ED30C8AF36F2355674BE8A1F2724CBEBD969ACC4937EA353A12F01E3E0D20$$$$$$Note$$$Update Notes$$$$$$PRTG intermediate version 25.1.104.1906$$$Please note that the intermediate version of PRTG that is needed for further software updates contains an issue for SSH sensors and SNMP v3 settings that could occur in certain cases. We recommend that you update to the latest released PRTG version 25.1.104.1961 that fixes the mentioned issues.$$$$$$Improved$$$Various$$$$$$All parts of PRTG$$$We updated the page PRTG Manual: Update from Previous Versions in our user manual.

March 18th 2025 - Version 25.1.104.1946$$$$$$New$$$Server$$$$$$Audit Logging$$$Subscription only$$$$$$We implemented the Audit Log feature with this PRTG version that is enabled when you have an according PRTG subscription license. You will see available settings under Core & Probes - Audit Log settings . Additionally; we updated the Send Syslog Message template in the Notification Templates. In order to meet the requirements for the transparency of security-related data in SIEM systems; this feature enables you to write audit logs to disk. You will find an according Audit Logs folder under C:\ProgramData\Paessler\PRTG Network Monitor\Logs\audit. Depending on your subscription; you might also have the possibility to export audit logs to a third-party system. Please note that this feature is only available if you run PRTG with a subscription license.

January 9th 2025 - 25.1.102.1373$$$Important$$$Security$$$Auto-Discovery$$$To address the attack described in CVE-2024-12833 (ZDI-24-1736; ZDI-CAN-23371); we hardened the auto-discovery process against possible injection of malicious content by adding additional validation and sanitization of input data; to mitigate the risk of a stored XSS (Cross-Site Scripting) vulnerability.

November 12th 2024 - Version 24.4.102.1351$$$$$$New$$$Sensors$$$$$$SNMP Disk Free v2$$$The SNMP Disk Free v2 sensor left its BETA status and is now fully supported. We introduced the SNMP Disk Free v2 as experimental sensor with PRTG version 23.3.86.1520. The SNMP Disk Free v2 sensor monitors the free disk space on a logical disk via the Simple Network Management Protocol (SNMP).$$$WMI Microsoft SQL Server 2022 sensor$$$To monitor Microsoft SQL Server as of version 2022; we implemented the WMI Microsoft SQL Server 2022 sensor (NEW). The WMI Microsoft SQL Server 2022 sensor monitors the performance of a Microsoft SQL Server via Windows Management Instrumentation (WMI).$$$$$$Changed$$$Server$$$$$$Geo location maps$$$We updated our API for maptiles and geocoding since the API from the location service provider has changed. In previous PRTG versions you would notice that there was no resolution anymore in some cases for your given geo location in the Location (for Geo Maps) and no map was displayed. This could have affected also new set geo locations while the old API was not working anymore.$$$$$$Important: Please note that in certain rare cases you will need to take further action to make your geo location map work again. For example; when you have added a location by address in the Location (for Geo Maps) while the old API was not working; you will need to enter a (space; character) again in the location field and the map is displayed correctly when you update to this PRTG version. However; if you have entered the address as coordinates in the map before; no further action is required.$$$$$$Changed$$$Sensors$$$$$$Secure Shell (SSH) sensors$$$We deprecated the option Run the command as a different user using su in the device settings for Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems for password security reasons. You will receive a corresponding TO DO ticket in PRTG that your action is required when you update to this PRTG version. For the SSH Rights Elevation method; please switch to the option Run the command as a different user using sudo (without password) instead for all affected devices.$$$$$$Improved$$$Security$$$$$$WebGUI$$$We hardened the PRTG web UI against possible Tabnabbing attacks. The CVSS v3.1 score for this vulnerability is 2.6 but specifically for PRTG the severity is calculated as Medium.$$$$$$Improved$$$Server$$$$$$API Keys$$$We added an endpoint to get information about an API key token with Token Type Desktop. The endpoint getdesktoptoken.htm with given authentication credentials will return a configured API key token for the type Desktop. In case there is none configured; the page will return a corresponding error message. In this case; you can also find the following log entry in the CoreWebserverLog: Webserver: Error: no Desktop-type token found.$$$Single Sign-on$$$PRTG now supports the Single Sign-on (SSO) capability through its auto-login function. This allows you to gain access to multiple systems that support Single Sign-on with a single login in the same browser. For example; if you have a PRTG instance configured with Single Sign-on Entra provider and you log in to the portal of your provider by using SSO; no further login (two factor authentication) is required when you want to log in to your PRTG. Upon logout; you will be redirected to the login page.$$$$$$Important: In certain cases you will not see a login page for Single Sign-on although you have configured and enabled it correctly in PRTG to use the new auto-login function. More precisely; this means if you want to log in with a different user account without using Single Sign-on or if the callback URI is wrong or invalid in the portal of the SSO provider (Entra or Okta). You will receive an error message; for example A silent sign-in request was sent but no user is signed in or The redirect URI (URI) specified in the request does not match the redirect URIs configured for the application (applicationID).$$$$$$If that happens; please use /public/local_login.htm for a

September 25th 2024 - Version 24.3.100.1361$$$$$$Improved$$$Server$$$$$$Update to OpenSSL 3.0.13$$$To ensure secure communication furthermore we updated to OpenSSL version 3.0.13 since OpenSSL also retired the 1.1.1 series end of September 2023. The following TLS versions will be supported in the connection security settings for Probe Connection and PRTG Web Server settings: TLS 1.3; TLS 1.2; TLS 1.1; TLS 1.0.$$$$$$Please note when you update to this PRTG version; that you cannot add new installations of mini probes because OpenSSL 1.0.2 is no longer supported. Existing installations of mini probes should not be affected. For more information please see our Knowledge Base article: What security features does PRTG include?$$$$$$Changed$$$Server$$$$$$Notifications$$$We changed the Teams Webhook feature for notifications Send Microsoft Teams Message in PRTG; since Microsoft will retire Office 365 connectors within Microsoft Teams. You can still use the former webhooks until their deprecation in 2025. Microsoft provides the new Workflows app that you can use for a workflow to post messages from a webhook request. With this PRTG version; Send Microsoft Teams Message notifications will now support Workflows webhooks that you can configure in your Microsoft Teams.$$$$$$For more information on how to set up your Teams notification in PRTG please see our Knowledge Base article: How do I create a webhook for the PRTG notifications to Slack and Microsoft Teams?$$$$$$Improved$$$Sensors$$$$$$Cisco Meraki Network Health sensor$$$We updated the API call that is used within the Cisco Meraki Network Health sensor since the formerly used API call /organizations/{organizationId}/devices/statuses was deprecated.$$$EXE/Script sensors$$$We improved the tooltip text information for the setting Parameters in the sensor Settings for EXE/Script and EXE/Script Advanced sensor types. If you hover over the tooltip icon for Parameters; you can see the following additional information: This setting can pose a security risk because sensitive information in the parameters appear in the sensor log. Use placeholders like %windowspassword or %scriptplaceholder1 to encrypt sensitive information and enable PowerShell Security Enhancement under Setup Monitoring Experimental Features to increase your security. This information is valid for the Result of Sensor [Sensor ID].Data.txt that is created when you have enabled the Result Handling option Store result in the sensor Settings.$$$FortiGate VPN Overview sensor$$$With this PRTG version we introduce the new Virtual Domain Settings (VDOM) where you can select the virtual domain that this sensor monitors during sensor creation. Existing sensors are unaffected as the setting will show the default value root.$$$HTTP v2$$$You are now able to include the HTTP v2 sensor in a device template when you have added the sensor to an appropriately configured device before. The device template is created when the HTTP endpoint returns status 200 (OK); using the same settings as the templated sensor. You can edit the device template afterwards if you need different status codes.$$$Probe stability$$$We improved the stability on PRTG probe level to avoid the risk of probe issues; such as access violations in the probe.log or a no longer working probe service.$$$$$$Fixed$$$Server$$$$$$API keys$$$We fixed an issue where changes via PRTG API v2 to any API key were not saved in the History tab of a user account. For example; when you created or modified an API key using /api/v2/users/api-keys/ endpoint; the changes would not be logged in your user account History tab.$$$PRTG probes$$$We fixed an issue that led to probes being disconnected from time to time when they were connected via communication protocol with very high latency.$$$$$$Fixed$$$Sensors$$$$$$DNS v2 sensor$$$We fixed an issue where the DNS v2 sensor with Query Type Host address IPv6 (AAAA) or Host address IPv4 (A) (default) only considered one IP address returned by a hostname instead of any matching IP address. For

July 31st 2024 – Version 24.3.98.1210$$$NEW$$$MULTI-PLATFORM PROBE 2.0.0+12481$$$New Features$$$This release introduces the device template capability for the multi-platform probe for certain sensors types. The device template file can only contain the sensors supported by the multi-platform probe and are device template capable; with some exceptions.$$$You can now use the feature Add Auto-Discovery Group on the multi-platform probe with the option Auto-Discovery with specific device templates or use the Run Auto-Discovery with Template on a certain device. This feature is only available for sensors supported by the multi-platform probe and for those that are device template capable; with a few exceptions.$$$You can now download and install the RPM packages directly from the package repository with your package manager. You can find the Paessler Linux package repository at Paessler Linux package repository.$$$With this release the multi-platform probe supports the experimental Cisco WLC Access Point Overview sensor.$$$For more information about the multi-platform probe and how to use it; please see Multi-Platform Probe for PRTG manual.$$$For detailed release notes about this release; see our Knowledge Base article: What are the release notes for the Multi-Platform Probe?.$$$IMPROVED$$$SECURITY$$$Webserver$$$With this PRTG version we provide various fixes to improve security and stability.$$$NEW$$$SENSORS$$$Script v2 sensor$$$The Script v2 sensor left its BETA status with this PRTG version and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 23.1.82.2074. The sensor executes a Python script that returns data in JSON format and shows the exit code. This way you can create your own custom script sensors that may not be available in PRTG by default. For available example scripts and how to use them; please see the Knowledge Base article: I want to use the Script v2 sensor example scripts. What do I need to know?$$$IMPROVED$$$SERVER$$$API keys$$$You are now able to delete created API keys under Account Settings in your PRTG Setup via multi-edit selection. Previously; API keys could only be deleted individually. For every API key that you delete; PRTG will add an entry in the History tab of your User Account settings.$$$Auto-discovery$$$You can now add multiple subnets to the auto discovery setting. If you want to include multiple addresses and subnets; enter them in the field IPv4 and Subnet (IPv4) as a list separated by a comma. Please note that this feature applies only for IPv4 subnets and does not support IPv6.$$$IMPROVED$$$SENSORS$$$NetApp v2 sensors$$$We updated the available lookup values for NetApp v2 sensors that were not supported in previous PRTG versions before. For example; the NetApp System Health v2 sensor now supports the values Tri Path; Tri Path HA and Virtual state for the status Up in the Storage Configuration Path channel. Other NetApp v2 sensors that have now addtional supported lookup values are NetApp SnapMirror v2 for the channels Mirror State and Policy Type and NetApp NIC v2 sensor for the channel State.$$$Microsoft Azure$$$With this PRTG version we introduce a new setting Microsoft Azure Management Endpoint in the Credentials for Microsoft Azure. This setting allows you to change the API endpoint for your region that can differ from the default URL management.azure.com to use Microsoft Azure sensors; such as Microsoft Azure SQL Database sensor or Microsoft Azure Storage Account sensor in your environment. Please note that this setting is locked by default and can be edited upon request.$$$Sensor message$$$We improved the error message for certain sensor types that appears when you need to check credentials or logfiles for a sensor. Affected sensors are AWS sensors; EXE/Script sensors; Zoom sensor; Veeam sensors; OPC UA sensors and Cloud sensors. The previous error message did not indicate that the setting for Store Result is not enabled by default and that you first need to enable it and

June 13th 2024 - Version 24.2.96.1346$$$$$$IMPROVED$$$VARIOUS$$$$$$Maintenance$$$PRTG version 24.2.96.1346 is a maintenance release with several code improvements necessary for upcoming PRTG versions.

Refer for full details - https://www.paessler.com/prtg/history/stable#24.2.96.1315$$$$$$IMPROVED$$$SECURITY$$$$$$Webserver$$$With this PRTG version we provide various fixes to improve security and stability.$$$$$$IMPROVED$$$SERVER$$$$$$Notifications$$$We improved the delivery time for HTTP notifications that took longer in certain cases in the previous PRTG versions when you used a HTTP target URL in the Execute HTTP Action section of the notification template. This issue occurred because the PRTG fallback handling for SSL still tried to establish a TLS secured connection what did not lead to an error but to a longer waiting time for PRTG.$$$$$$IMPROVED$$$SENSORS$$$$$$Ping v2$$$You are now able to create the Ping v2 sensor via device template if you select the option Create Device Template on a device where you can select the Ping v2 sensor in the Create Device Template dialogue window. The Ping v2 sensor left its BETA status with PRTG version 24.1.92.1554 and is now fully supported.$$$$$$IMPROVED$$$MULTI-PLATFORM PROBE$$$$$$Probe Adapter$$$You will now receive a proper error message in the probe adapter log when your NATS server for connection does not offer a secured TLS connection but PRTG is configured to connect with TLS in the Multi-Platform Probe Connection Settings.$$$$$$FIXED$$$SERVER$$$$$$Contact support$$$We fixed an issue where the button Contact Support was missing in the help bar and also in the Support section on the PRTG Setup page when you ran PRTG with a trial license. This issue also affected Paessler PRTG Hosted Monitor.$$$Cluster$$$We fixed an issue where the API call for api/health.json reported wrongly a disconnected Cluster probe although the probe was connected at this time. You could also see this behavior on the System Status page in PRTG under Probes where the Cluster Probe was reported as not connected yet.$$$Libraries$$$You can now filter for a specific sensor type when you select Add Library Node for your library and when you choose the option Show a collection of filtered sensors and Show only specific sensor types for that node. In previous PRTG versions; when you filtered for the sensor type SSL Certificate sensor; the SSL Security Check sensor would be added to the node as well; for example.$$$Maps$$$We fixed an issue for public maps access that allowed users to see objects in the device tree despite of their assigned security context when you had two or more public maps open in a tab for map rotation view.$$$PRTG Administration Tool$$$You will no longer receive an error when you click on the button Stop Service or Start Service (ignore changed settings) for the Core and Probe service in the PRTG Administration Tool when you run it as a 64bit version on your system. This issue occurred in the previous PRTG stable version 24.2.94.1400 but did not happen when you run the PRTG Administration Tool in a 32bit mode. The reported error message in this case was One or more required program components of PRTG (PRTG Server; PRTG Probe) could not be found! Please re-run the installation program.$$$Search$$$You will now receive proper results from our Help documentation when you click on the More button on the Search Results page. This did not work in the previous PRTG versions and returned the message Your search request did not return any results (Help Documents) when you; for example; searched for the term Core Health. You could also see that your seach term was not resolved properly and displayed as core%20health.$$$Single Sign-on$$$You are now able to send a support bundle with all relevant files via Contact Support button on the Setup page when you are logged in to PRTG with a Single Sign-on user account. In the previous PRTG versions; sending a support bundle as a logged in Single Sign-on user would trigger the overload protection in PRTG and the bundle would not contain any htm files.$$$XML tables$$$We fixed an issue where the returned table for a queried XML was broken when you had an object; e.g. sensor; with a tag that containe

We fixed an issue with PRTG version 24.2.94.1400 where the Probe update to this PRTG version failed and therefore the Probe service(s) did not start in some cases. PRTG would report an error message like PRTG probe service could not be startet: The service did not respond to the start or control request in a timely fashion or Windows could not start the PRTG Porbe Service service on Local Computer Error 1053: The Service did not respond to the start or could request in a timely fashion when you were affected by this issue. In some rare cases also the Core service was affected when you updated to PRTG stable version 24.2.94.1400. The issue occurred because Windows tried to load the certificate cache what took too long for the Probes during startup and caused a timeout. This issue also affected new installations of PRTG.

Refer the link: https://www.paessler.com/prtg/history/stable#24.1.92.1554

ITOps Board version 3.13 comes with accessibility enhancements. In this release; the Explorer tab has been updated for accessibility and now includes text labels to indicate the health state of each component. Additionally this release introduces the use of icons to indicate the health state of components and alerts. It also covers fixed issues. For more information please refer to the release notes provided with the new version.$$$$$$Important Notice: Upgrade Process. The ITOps Board installer supports an in-place upgrade. If you made manual changes to the web.config file; those changes are not preserved during an in-place upgrade. Any manual changes to the web.config file are saved in a file with a name that uses the following format: Web-YYYY-MM-DD.config. Before you begin an upgrade; save a copy of this file. It is recommended that you use the file as reference to make changes to the new web.config file; which will overwrite the previous file during the upgrade process. Do not overwrite the new web.config file with the old file.$$$This release of ITOps Board requires Elasticsearch version 7.17.6.